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.

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.

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

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.

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.

This is completely at the discretion of the admin.

While it's not possible to entirely disable or block access to Autodesk Drive, administrators do have the option to limit access to Drive to 'Read Only'.

As soon as a user is removed from your system, they will lose access to Autodesk products and services.

Before beginning SSO setup, you should confirm that the following fields contain a value for all users in your identity provider: first name, last name, email, and a field that can be set as ObjectGUID.

If you use Active Directory Federation Services (ADFS), you can trace the reason for sign-in failures by examining event logs.