APIs & Integrations
Microsoft Tenant Specific Endpoints
Overview
Pre-built tooling
Pre-built integrations
No pre-built integration yet (time to contribute: <48h)
Not seeing the integration you need? Build your own independently.
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
Setup guide
No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Useful links
- Create an Azure app registration for the specific application.
- Add permissions for the appropriate app on the
API Permissions
tab
- Add permissions for the appropriate app on the
- OAuth-related docs.
- See particularly the
tenant
parameter under Request an authorization code. Thistenant
parameter must be provided as extra configuration to the frontend SDK.
- See particularly the
- List of OAuth scopes
- The specific scopes required will depend on the application being accessed. This might use the .default scope with the resource’s identifier URI.
Contribute useful links by editing this page
This endpoint supports services authorized using an Azure App Registration in any accessible tenant, including:
- Microsoft Dynamics 365 Finance and Operations
You can use this provider for general Microsoft Graph access (and the major Microsoft SaaS services like Teams, OneDrive, other Office 365 services, etc.) by setting the
tenant
to common
but we recommend using the Microsoft Teams provider instead which includes sync capability.API gotchas
- If you are developing an app for users within your own organization and the app has already been granted adequate permissions at the organization level with user consent turned off, you must override the integration config when calling the create connect session method:
- Override
authorization_params
by setting onlyscope: '.default'
and"prompt": ""
to remove the consent screen. Note that if consent is required it will prompt the user for consent due to the “.default” scope. - Override
authorization_params
by setting onlyscope: '.default offline_access'
and"prompt": ""
to remove the consent screen. Note that if consent is required it will prompt the user for consent due to the “.default” scope. - Set the
.default
scope documentation to ensure the permissions remain the same as those granted at the organization level.
- Override
If this is not done, the app will show a consent screen prompting the user to grant permissions which the user will be unable to do without admin access.
Add Getting Started links and Gotchas by editing this page