Enabling SSO for a global domain locks out users in other regions

Issue:
Autodesk SSO integration is enabled for your global domain and is working without issue in your primary geographic region. However, users in other geographic regions are locked out as if SSO is not enabled for them even though they use the same domain in their email addresses.


Causes:
The domain is used around the world, however in each regional location that uses Autodesk, they may have their own subscription tenant with their own assigned licenses for that particular region.  It is unclear why this scenario causes the failure at this time.

Solution:
Currently the workaround is to add users from the other region to the U.S. tenant (or whichever your primary region is), and then this satisfies the SSO requirement.  You would only be adding the users as part of the team for the primary account and would NOT be assigning the actual licensing from this account.  Instead, the licensing and assignments for these users would still be assigned from their regional subscriptions on their own teams.  In each instance where this has occurred, this has been the solution that has resolved the issue for clients.

Reference for licensing:

https://www.autodesk.com/company/terms-of-use/en/offering-types-and-benefits  

https://damassets.autodesk.net/content/dam/autodesk/docs/company/GUR_Approved_Country_List_ENG_update_06162022.pdf

About the Author

Heath White

Sr. Technical Support Specialist, Manufacturing

Follow on Linkedin More Content by Heath White
Previous Article
Making Each Instance a Separate Line in Inventor BOMs
Making Each Instance a Separate Line in Inventor BOMs

How to make each instance a separate line in Inventor BOMs

Next Video
Managing Civil 3D Project Data in the Cloud - Part 4
Managing Civil 3D Project Data in the Cloud - Part 4

Learn how to get up and running using Autodesk’s cloud platform to host/manage Civil 3D projects.

Need tech support? Let us help!

Learn More