![]() In Azure AD the logs looked like this: Azure AD sign-in for Adobe Creative Cloud (identified as Chrome 105) and Office via the browser (Chrome 112) We rolled out the two above extensions via Group Policy and they were turned on in Chrome, but login was still failing – and incidentally, the Chrome sign-in was version 112 and showing a successful sign-in as the extensions where working and device identity was happening. Adobe Creative Cloud in Azure AD – identified as Chrome 105 on a non-company deviceīut as we can see above, the Azure AD sign-in logs show that it is Chrome 105 and not compliant or managed (as there is no Device ID associated with the login) so CloudAPAuthEnabled is not an option we can try. To get Chrome to pass through the device identity to Azure AD (so that managed or compliant can be evaluated) requires the installation of the Windows Accounts extension or the Microsoft 365 extension, or after Chrome 111 the CloudAPAuthEnabled option. In Azure AD this popup is identified as Chrome 105 (the latest version of Chrome at time of writing is 113). The popup is a web browser control, but not a full browser. And this is what we found for Adobe Creative Cloud.Īdobe Creative Cloud to sign-in presents a popup inside the application. One is to exempt that app from the “only company machines” rule (and maybe have a different rule in place) or see if there is another way to authenticate the user on that device for that app. Conditional Access approves or rejects the login based on that knowledge – so what happens if the app in question is running on a company (managed or compliant) machine, but the app does not pass that information through to Azure AD? Your login will be rejected is what happens! So, I recommend resetting the clock before your trip, and then again along the way based on the grace period available to you.In Azure Active Directory it is possible to create Conditional Access rules that restrict applications to only running on company owned or managed devices. ![]() You can also reset that clock before your trip to help ensure you’ll have as much time as possible working offline before you need to validate your subscription again. If you’re traveling offline for a period of time that exceeds the grace period at some point during the trip, you’ll need to get online to reset the clock. If you want to change your plan to the annual option, you will need to contact Adobe support directly to make this change. There is a 30-day grace period for monthly Creative Cloud subscribers and a 99-day grace period for annual subscribers. More Detail: Adobe applications require that you validate your subscription via an internet connection. You can extend this to a 99-day grace period by switching to an annual plan rather than monthly. Tim’s Quick Answer: If you have a monthly subscription you will need to connect to the internet at least every 30 days. ![]() Is there anything I need to do to be sure I have access while being offline for such a period of time? Today’s Question: I am expecting to be working in a very remote location for about five weeks and want to be sure I will be able to access Lightroom Classic and Photoshop on my laptop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |