How to connect Microsoft 365

Not everyone has this

Microsoft 365 is an optional module. If you can’t see it in the menu, it isn’t switched on for your workspace. Ask an admin to turn it on under Settings ▸ Features.

Admins only

You need the Admin role to do this. Admins are set in Settings ▸ Users & Access. If you don’t see the screens below, ask an admin in your organization.

Connecting Microsoft 365 brings tenant usage, licensing and security data into CloudMonitor alongside your cloud spend.

Before you start

You need a Global Administrator on the Microsoft 365 tenant to approve the consent. If that isn’t you, get them alongside you: the approval happens on Microsoft’s own screen and can’t be delegated from here.

Step 1: Find the connector

Settings ▸ Sources & Integrations ▸ expand Microsoft 365.

If there’s no live data yet you’ll see Connect Microsoft 365 with a Connect button.

Step 2: Check the tenant ID

The dialog asks for your Microsoft Entra tenant ID:

The tenant that owns your Microsoft 365 data. Pre-filled from your sign-in, so change it if you administer a different tenant.

It’s pre-filled from your sign-in, so usually you leave it alone. Change it only if the Microsoft 365 tenant genuinely differs from the one you signed in with.

It’s a 36-character GUID. You’ll find it in the Entra admin center under Overview ▸ Tenant ID. Get it wrong and the button stays disabled with Enter a valid tenant ID first.

Step 3: Review what you’re granting

The dialog lists every permission and why it’s needed. All of them are read-only: CloudMonitor never writes to your tenant and never stores a credential.

Worth actually reading rather than clicking past: it’s the list your security team will ask about, and it’s shorter than you’d expect.

Step 4: Authorize

Authorize CloudMonitor opens Microsoft’s consent screen in a new tab. A Global Administrator approves it there.

If nothing opens

CloudMonitor runs inside a Microsoft Fabric frame, which blocks ordinary pop-ups, so the link is opened a different way. If your browser still swallows it, allow pop-ups for this site and try again.

Step 5: Wait for the first sync

Back in CloudMonitor the row shows Authorization pending until data arrives, which happens on the next daily sync rather than immediately.

The flag clears itself once real data lands. If it’s still pending after a couple of days, the consent probably wasn’t completed. Run through it again.

Disconnect or reconnect Microsoft 365

Expand the connected Microsoft 365 source and select Disconnect. CloudMonitor cannot remove a tenant-wide grant itself. The dialog identifies the enterprise application and opens Microsoft Entra so a Global Administrator or Cloud Application Administrator can revoke admin consent. Deleting the enterprise application also removes the consent.

After you open Entra, the source shows Revocation pending verification. Existing Microsoft 365 data stays in your workspace, and revoking consent stops future collection at Microsoft. The current screen cannot verify the revocation yet, so the verification control remains unavailable and this status is an interim marker.

Select Reconnect if you want to restore access. Approve consent again on Microsoft’s screen. The source shows Reconnection pending. The current screen cannot verify restored access yet, and existing data on its own does not prove that the new grant worked. Check that new data arrives after the next daily sync.

If Microsoft 365 says “Not configured”

The connector hasn’t been enabled for your workspace at the platform level, which isn’t something an admin can change here. Contact support.

Connect GitHub Copilot

GitHub also has a self-service connection when the Tokenomics module is on.

1. Find GitHub under Settings ▸ Sources & Integrations, then select Connect.
2. Select Install on GitHub. A GitHub organization owner installs the CloudMonitor app. If you are not an owner, GitHub can send them an approval request.
3. Return to CloudMonitor and select I’ve installed it.
4. Enter the GitHub organization name from its URL. For github.com/acme-corp, enter acme-corp, not the display name.
5. Select Connect GitHub.

The GitHub app grants read-only access to Copilot billing. It does not read your code. CloudMonitor checks the shape of the organization name, but it cannot confirm that the organization exists or that the app was installed there. A correctly formatted typo saves without an error and collects nothing.

Connecting also switches on the GitHub Copilot module. The source shows Connection pending until Copilot data arrives after the next daily sync.

Disconnect or reconnect GitHub

Expand GitHub and select Disconnect GitHub. Collection stops at the next daily sync. Data already collected stays in your workspace, and the GitHub Copilot module stays switched on.

CloudMonitor keeps the organization name and does not uninstall the GitHub app. Reconnect opens the saved organization directly, so you can confirm it without repeating the installation step. To remove the app as well, uninstall it from the organization’s GitHub settings.

The other connectors

Cursor, Anthropic and OpenAI appear as sources when the Tokenomics module is on, and Azure is always there as the core cost feed.

Microsoft 365 and GitHub have self-service connection flows. The other providers show their current status once data is arriving, but they are set up outside the app. Contact support to have one enabled.

Checking it worked

The Your data card on the same screen lists the tables CloudMonitor reads, with live row counts. It’s the quickest way to confirm data is genuinely flowing rather than just consented.