Before you start
- You need permission to manage companies or integration company mappings.
- A Microsoft 365 administrator for each client tenant must be available to approve the permissions, or you must have admin credentials for that tenant.
- Your rollout companies must exist in MSPortal.
- Allow pop-ups for MSPortal. Consent opens in a pop-up window.
Connect each company
1
Open the companies list
In Launch Center, open Connect other tools, tick Microsoft 365 under Productivity, and click Open on its card. Then click Open setup in Settings. You can also go to Settings > Integrations > Microsoft 365 > Companies.
2
Find the company
Use Search companies… or the filter to find the rollout company. Check that you are on the right company and Microsoft tenant before you connect. Check existing mappings before you create another connection.
3
Click Connect
Click Connect on the company’s row. A pop-up opens the Microsoft sign-in page.
4
Sign in and approve
Sign in with an administrator account from the client’s Microsoft 365 tenant. Read the permissions on the Microsoft consent screen and the target tenant, then approve. Finish any acknowledgment MSPortal shows first. The pop-up closes and the list refreshes.
5
Check the connection
Confirm the row shows Connected with the right Microsoft tenant. A pop-up that closed is not proof of a healthy connection.
6
Repeat for each company
Work down your rollout companies.
Check the data
1
Look at the sync
Check Last synced on the row. It covers users and groups. For licenses and Secure Score, open the Cloud page for that company.
2
Set up client users
Importing users and assigning access is separate from consent. See Prepare Company users. To create Company users automatically after each sync, add an import rule in Access rules. User import on the companies list shows whether each tenant takes part.
3
Check Launch Center
Back in Launch Center, check the Microsoft 365 card on Connect other tools. It shows Ready once at least one company has a healthy connection, and Needs attention when connections exist but none is healthy.
Match the rollout scope
Start with the intended pilot company, then review each additional company you plan to launch. Connecting one company does not connect the others, and the Ready status on the card does not replace a review of every company connection. Connect only the companies you intend to enable. Do not connect an unrelated tenant just to change a status.Troubleshooting
Frequently asked questions
Does one Microsoft 365 connection complete a wider rollout?
Does one Microsoft 365 connection complete a wider rollout?
No. Every company you plan to enable needs its own healthy connection. Review the saved connection and expected data for each one.
Does consent give imported users portal access?
Does consent give imported users portal access?
No. Import users, assign a company, and choose an access group separately, or let an access rule import them. Imported users still need an invitation or their first sign-in.
Does the pop-up closing prove the connection works?
Does the pop-up closing prove the connection works?
No. Check that the row shows Connected, then check the sync.