Microsoft 365

Microsoft 365 is a cloud-based productivity platform. It provides a suite of online products such as Microsoft Teams, Word, Excel, PowerPoint, Outlook, OneDrive, and more.

In order to integrate Microsoft 365 with Relyance AI you will need to follow an OAuth2 flow.

In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the Microsoft 365 integration card and click on it.
5. Click on the Add Connection button on the top right.
6. Provide a meaningful name for the integration and click on the Add button.
7. In the Overview section, select the integration features you wish to enable for the integration, review the Scope and Permission, and Endpoint details and click on Continue. For more details, seeIntegration Features.
8. In the Connection section, provide the appropriate values and click on Continue,
   • Connection Name: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by Discovery Source across the Inventory, Visual Maps, Assets, and Data Flow Analysis pages.
   • Rescan Frequency: This property allows you to configure how often Relyance executes scans against this Vendor connection.
   • Business Atlas Associations (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the Select Associations dropdown — the wizard will not advance past this step without one. For more details, see Business Atlas.
9. In the Authentication section, OAuth/App Token is available as default selection, please click on Continue.
10. Review the configuration summary from the Completion section and click on Finish.
11. Confirm the integration Status reflects Connected.

Authentication methods and fields

Pick one of these under Authentication Method on the connection wizard's Authentication step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

Verify the connection is really working

1. Connected but nothing discovered is admin consent on User.Read.All.
2. Data subject requests fail while discovery works. DSR handling needs User.ReadWrite.All and Directory.ReadWrite.All — write scopes, granted separately from the read-only discovery scope. Enabling the DSR feature without adding and re-consenting them leaves requests failing while everything else looks healthy.
3. offline_access is what keeps the connection alive. Without it the refresh token is not issued and the connection stops at the first token expiry, typically an hour in, which reads as an intermittent fault rather than a missing scope.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example microsoft365/<connection_id>) or reading it with the relyance_integration_connection data source.