Microsoft Applications with Client Credentials integration updates
The Azure Client Credentials, Dynamics 365 Client Credentials, and Office 365 Client Credentials integration instructions were updated. For details, see:
| • | Information stored |
| • | Minimum permissions |
| • | Authentication method |
The following integration tasks now store additional information.
| • | Azure Client Credentials application discovery |
| • | Azure Client Credentials SSO Application Roster |
| • | Azure Client Credentials SSO Application Access |
| • | Dynamics 365 and Office 365 Client Credentials Application Roster |
| • | Dynamics 365 Client Credentials application access |
Azure Client Credentials application discovery
The following information was added:
| • | App Instance ID |
| • | Additional Details (open_access, publisher, oauth2Integration) |
Azure Client Credentials SSO Application Roster
App Instance ID was added.
Azure Client Credentials SSO Application Access
Occurred was replaced with Last Login.
Notes was replaced with Login Location.
Dynamics 365 and Office 365 Client Credentials Application Roster
User ID was replaced with User ID (User Principal Name).
Dynamics 365 Client Credentials application access
User ID was replaced with User ID (User Principal Name).
Last Login was added.
For Dynamics 365 Client Credentials, the “Notes” field was removed.
The Global Administrator role is required to grant the application permissions. For details, refer to the Microsoft documentation Azure AD Built-In Roles.
The authentication method for integrating Azure Client Credentials, Dynamics 365 Client Credentials, and Office 365 Client Credentials with SaaS Management is OAuth2 with Client Credentials. For details, refer to Microsoft’s instructions in Microsoft identity platform and OAuth 2.0 client credentials flow.