Since Office 365 17.2, the procedure of configuring pre-consent for a Graph API native app is part of the Odin Automation Office 365 Integration Provider's Guide.

If you need to configure or re-configure pre-consent for a Graph API native app, refer to the following sections:

  • Microsoft Cloud. See oap_office_365_integration_17.2_providers_guide.pdf's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing CSP Account > Registering Native Apps for Partner Center and Graph APIs > Microsoft Cloud.

  • Office 365 Operated by 21Vianet in China. See oap_office_365_integration_17.2_providers_guide.pdf's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing CSP Account > Registering Native Apps for Partner Center and Graph APIs > Office 365 Operated by 21Vianet in China.

  • Microsoft Cloud Germany. See oap_office_365_integration_17.2_providers_guide.pdf's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing CSP Account > Registering Native Apps for Partner Center and Graph APIs > Microsoft Cloud Germany.

After configuring pre-consent for your Graph API native app, validate that your Office 365 application and your Office 365 application instance have necessary access to the Graph API:

  1. Create a customer account with an Office 365 subscription, and then log in as the customer. Note that the subscription must contain Office 365 resources of the application instance being validated.
  2. Add a user.
  3. Assign an Office 365 license to the user.
  4. Add a domain to Office 365.

All of the operations must be successfully completed (no errors, no failed tasks).

Internal content