There are two configuration steps:
- Register your application - this step creates an Application ID and specifies the authentication type used to login to your applications.
- Add API permissions - this step adds the permissions Microsoft Office 365 activities need to interact with your application.
Follow the steps listed below to register your application.
The steps listed below are sourced from Register a new application using the Azure portal in the Microsoft Azure documentation.
- Sign in to the Azure portal using your personal, work, or school Microsoft Office 365 account.
- In the left-hand navigation panel, click Azure Active Directory.
- After the Azure Active Directory page opens, click App registrations.
- Click + New registration in the top navigation bar.
- Enter a Name for your application (e.g., "Office365App").
- Under Supported account types, select "Accounts in any organizational directory".
- Under Redirect URI (optional), select "Public client (mobile & desktop)" and enter "urn:ietf:wg:oauth:2.0:oob" as the URI address.
While the example redirect URI provided (urn:ietf:wg:oauth:2.0:oob) should work for personal, work and, school Microsoft Office 365 accounts, we recommend consulting your IT department to confirm the value you should use.
For more information regarding the redirect URI and authentication, see the following resources in the Microsoft Azure documentation:
- Click Register.
You're done! Now, let's add API permissions to your registered application.
Follow the steps listed below to add API permissions to your registered application.
The steps listed below are sourced from Add permissions to access web APIs in the Microsoft Azure documentation.
- From your registered application page (Azure portal > Azure Active Directory > App registrations > Office365App), click API permissions in the left-hand navigation panel.
- After the API permission page opens, click + Add a permission (this opens the Request API permissions window).
- Under Select an API, click Microsoft APIs (may be open by default).
- Under Commonly used Microsoft APIs, click Microsoft Graph.
- Under What type of permissions does your application require?, click Delegated permissions to show the list of permissions.
The differences between Application permissions and Delegated permissions are bolded below:
Application permissions - Your client application needs to access the web API directly as itself (no user context). This type of permission requires administrator consent and is also not available for public (desktop and mobile) client applications.
Delegated permissions - Your client application needs to access the web API as the signed-in user, but with access limited by the selected permission. This type of permission can be granted by a user unless the permission requires administrator consent.
For more information, see Configure a client application to access web APIs in the Microsoft Azure documentation.
- Scroll down the alphabetical list of permissions and click Calendars.
- Select Calendars.ReadWrite.
- Scroll down the alphabetical list of permissions and click Files.
- Select Files.ReadWrite.All.
- Continue scrolling down and click Mail.
- Select Mail.ReadWrite.Shared, Mail.Send and Mail.Send.Shared.
- Click Add permissions (returning you to your list of API permissions)
- Verify your API permissions include your added Calendars, Files, and Mail permissions.
At the top of the API permissions list page, a note (marked with a * in the image above), stating "Permissions have changed. Users and/or admins will have to consent even if they have already done so previously", indicates that you need to consent to the application's delegated permissions when you first run a Microsoft Office 365 activity with this registered application.
For more information, see Consent framework in the Microsoft Azure documentation.
For an example of the consent experience, see Consent experience - an example in the Microsoft Azure documentation.
Now that you have registered your application and added API permissions, you can build automation projects that include Microsoft Office 365 activities.
To get started and validate your configuration settings work, follow the Quickstart guide to build your first Microsoft Office 365 automation project.