Will Autodesk products send Device ID to my identity provider when signing in on desktop?.

The objectGUID is used to identify unique users.

The team you have selected when setting up your SSO and directory sync connections will be the team that the users are added too.

Binding refers to the mechanism used to transmit authentication data between the identity provider and service provider (Autodesk).

As we start mapping, in most systems we will require First and Last Names, User Name, Email and Unique ID.

This is completely at the discretion of the admin.

When a user has more than one email address in your system, you may want to set email mapping to User Principal Name (UPN) to avoid confusion between primary and secondary emails.

With SSO, users are identified by their objectGUID, which isn’t dependent on their username.

The following diagram provides a high-level overview of the SSO sign-in sequence and components.

Yes, while synced groups created by directory sync are read-only, you are able to grant software access to users within these groups by assigning software and services at the group level.

Autodesk SSO recognizes the new domain of the same user, provided the customer continues to have the specific information aligned to the predefined criteria of the Autodesk system.

No. SSO requires a registered domain that can be verified by Autodesk.

The Manage SSO button in the same team appears disabled, when directory sync is set up using an SSO connection from another team.

What is Just-In-Time Provisioning? Just-In-Time (JIT) provisioning is an automated process that creates and configures user accounts when they sign in for the first time.

SSO lets users sign in to Autodesk using their organization’s email address instead of creating and remembering a separate Autodesk username and password.