Follow

Registering an Azure Application for use with the Exchange 365, Teams and OneDrive Connectors

Created by: Jerry Thiesen
Created date:
Last Updated date:

Background

This will walk you through registering an Azure application that can be used by the Microsoft Office 365, Teams and OneDrive connectors in FTK Central, eDiscovery, and Enterprise.

 

Prerequisites

  • FTK Central, eDiscovery 7.1.1 SP4 or newer, Enterprise 7.4.2 or newer
  • O365 Global Admin credentials for your organization

 

Procedure

      1. Log in to the Azure Portal at https://portal.azure.com with Global Admin credentials
      2. Click on App registrations (this can also be found via the Search Resources... bar at the top of the page)mceclip2.png
      3. On the App Registrations Page, click New registration
        mceclip7.png
      4. Do the following:
        1. Provide an application Name
        2. Under Supported account types select Accounts in any organizational directory (Any Azure AD directory - Multitenant)
        3. Click Register
          2021-06-23_10_05_23-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      5. From the Application Overview page, click Authentication on the left
        2021-06-23_10_16_31-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      6. Under Platform configurations, click Add a platform
        2021-06-23_10_08_37-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      7. Click Web on the right
        2021-06-23_10_10_03-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      8. Under Redirect URI, enter one of the following URLs and click Configure:

        • eDiscovery (all connectors): https://localhost/accessdata

        • FTK Central/Enterprise (Exchange 365): https://localhost:4443/api/GraphApiAccessDataAdmin

        • FTK Central/Enterprise (Teams): https://localhost:4443/api/MicrosoftTeamsAccessData

        • FTK Central/Enterprise (OneDrive): https://localhost:4443/api/OneDriveAccessData
          Note: If FTK Central is using a custom port, change this URI to reflect that
          2021-06-23_10_13_58-mRemoteNG_-_confCons.xml_-_ftkc-app.png

      9. If you will be using this Azure app for multiple connectors, back on the Authentication page, click Add URI, and add any additional URLs from step 8 as necessary, then click Save
        2021-06-23_10_19_27-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      10. Click Overview on the left
        2021-06-23_10_21_44-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      11. At the Overview page, copy the Application (client) ID for future use
        2021-06-23_10_24_19-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      12. Click Certificates & Secrets on the left
        2021-06-23_10_25_44-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      13. On the lower half of the page, click New client secret
        2021-06-23_10_41_04-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      14. Do the following:
        1. Provide a Description for the client secret
        2. In the Expires drop-down, select an expiration date for the client secret
          Note: We do not provide a recommendation on the life of the secret. This is a security consideration that is dependent on each organizations security posture and internal requirements.
        3. Click Add
          2021-06-23_10_47_11-Window.png
      15. Copy the generated Secret Value for future use
        2021-06-23_12_04_29-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      16. Click Manifest on the left
        2021-06-23_10_50_49-mRemoteNG_-_confCons.xml_-_ftkc-app.png
      17. Highlight and copy the entire JSON definition in the Manifest Editor, paste it in the box below, and click Submit.  This will insert the necessary permissions into the manifest JSON in order to work with the connectors.


      18. Highlight and copy the entire JSON definition from the box below, paste it into the Manifest Editor (replacing all existing contents) and click Save in the upper left.

      19. From the left hand side, select API permissions
        mceclip0.png
      20. Click the Grant consent button, and wait for all rows under the Status column to report that consent has been granted.
        mceclip1.png
        mceclip2.png

Your Azure application can now be used for the desired connectors.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk