Microsoft Azure Setup for Microsoft 365 Hyland Outlook Office Add-In - Microsoft 365 Hyland Outlook Office Add-In - 1.0 - 1.0 - Other - external

Microsoft 365 Hyland Outlook Office Add-In

Platform
Other
Product
Microsoft 365 Hyland Outlook Office Add-In
Release
1.0
License

The Client ID and Secret value need to be set up within Microsoft Azure for use on the Administration Configuration page and deploying the Microsoft 365 Hyland Outlook Office Add-In.

To register and configure an application with appropriate settings and to add to Microsoft Azure tenant, complete the following steps:
  1. Add a new application and get the Application Client ID, during the application registration process.
  2. Generate a Client Secret in the Certificates and secrets section.
  3. Copy the value of the Client Secret as you will not be able to retrieve it again.
    Note: The Client ID and the Secret are used while configuring tenant information and generating a manifest xml file in the Configuration Overview section.
    Note: The Azure Client Secret has an expiration. The system administrator must update this secret in Azure and apply the new client secret in the Outlook Add-in Admin site when it is set to expire.
  4. Configure the appropriate API settings within the Expose an API section. The Application ID URI must include the fully qualified domain name where the add-in is installed. (see Installing the Add-In ). Also, add the following required Scope:
    • access_as_user
  5. Add a Client Application and authorize the scope for a specific Office Client Application ID.
    For more information on which application client ID to configure, see Microsoft’s Identity Platform documentation.
  6. Configure API Permissions in the API Permissions section and grant admin consent.
    • Mail.Read
    • openid
    • profile
    • User.Read
    The Mail.Read API permission must be set in azure to grant consent for attempts to import within the add in.
    If the Administrator does not grant Administrative consent within the Azure portal, the Add-In will prompt a user to grant consent when attempting to import a document. Only administrators will be able to grant consent.
    Note: These permissions are all Microsoft Graph delegated permissions. These permissions must match the scopes listed under the WebApplicationInfo section of the Add-in manifest XML file that is generated from the Administration Configuration Page.
  7. Add a Web application platform configuration and enter the example URI.

    Example: https://[my.domain.com]/[Add-inVirtualDirectory]/auth-response