Before you start
- The connector is a Microsoft-validated integration from Go Autonomous, a Microsoft Partner. It sources emails in the background — it won’t disrupt end-user workflows.
- Microsoft authentication requires an IT representative with Azure Active Directory admin rights.
- Setup typically takes around three minutes. After permissions are granted, allow up to ten minutes for the connector to appear on the Go Autonomous platform.
- Once available, inbox selection can be completed without further IT involvement.
Set up security groups
Requires Microsoft Azure AD admin rights.
- Official Microsoft guide: limit application permissions to specific Exchange Online mailboxes
- Microsoft Admin Center — set up security groups
Enable the Microsoft connector
Requires Microsoft Azure AD admin rights and Go Autonomous admin rights.
Log in to Go Autonomous
Navigate to my.goautonomous.io and enter the credentials provided by your Go Autonomous Success Manager.
Navigate to Company Settings
Click the menu button in the upper right corner of the screen and open Company Settings.
Add the Microsoft connector
Navigate to Connectors and click the Microsoft connector under Add connection.
Log in with Microsoft admin credentials
A standard Microsoft authentication prompt will appear. Enter your Microsoft admin credentials. Microsoft handles all credential processing — Go Autonomous does not have visibility into them.

Accept permissions
Click Accept to authorise the connector. You will see a Success! confirmation screen.

Set up inbox sourcing
Requires the Microsoft connector to be activated (Part B) and Go Autonomous admin rights.
Open the active connector
Navigate to Administration > Company Settings > Connectors and click the established Microsoft connector.
Troubleshooting
I don't see the desired inboxes available for connection.
I don't see the desired inboxes available for connection.
Check that the following requirements are met:
- The inbox is part of a security group created in Part A.
- The inbox name is spelled exactly as it appears in Azure Active Directory (including upper and lower case).
- If the inbox has aliases, try searching for those as well.
I connected the inbox but emails are not coming into Go Autonomous.
I connected the inbox but emails are not coming into Go Autonomous.
Check whether incoming emails are being automatically moved by Outlook to a subfolder of the inbox. Go Autonomous sources from the root inbox only.
SSO and user access
Setting up the Microsoft connector also establishes the SSO connection between Go Autonomous and your Azure tenant. From this point, users sign in to Go Autonomous with their Microsoft credentials. Once SSO is in place, you control who can access Go Autonomous directly from Azure — by managing access to the Go Autonomous Enterprise Application in your Azure user groups. Anyone you assign to the application can sign in; anyone you remove loses access.Sync user groups to control in-platform privileges
You can take this one step further and sync Azure user groups into Go Autonomous so that what users can do inside the platform is also driven from Azure. When a user signs in for the first time, their group membership in Azure determines the user groups (and therefore the permissions) they inherit on the platform — no manual provisioning needed.- User Groups — how user groups work in Go Autonomous and what each group controls.
- Setting up SCIM — sync user groups from Azure (Microsoft Entra) into Go Autonomous via SCIM.
- User Management — see synced users and their effective permissions.