Search Engine: Elastic
  • Article for your preferred language does not exist. Below is international version of the article.

Article ID: 126807, created on Sep 4, 2015, last review on Dec 20, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 6.0
  • Business Automation 7.0
  • Business Automation 7.1
  • Business Automation 7.2
  • Business Automation 6.0
  • APS 2.x

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:

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).

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 c0f836394088a28cc30dd0e5fe8b600e b2c3b33425dfc50c7d41a2efaa7f84f3 717db81efe94e616312b74fb03a5d474 70bf700e0cdb9d7211df2595ef7276ab 7c0b495571a6c1bec50e4f324a20ec14 ef171e3fccb12bd8e09076a7b49212c0 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF