Weavestream
Start Self-Hosting View on GitHub
3 min read

Bring Microsoft 365 Into Your Client Documentation

Connect Microsoft 365 to Weavestream to document users, licenses, storage, Intune devices, security information, and domains alongside the rest of each client's environment.

microsoft-365integrationsmspit-documentationself-hosted
01 / Post3 min read · 591 words

A client asks which accounts still have licenses, whether a laptop is managed, and how close a mailbox is to its storage limit. The answers exist, but they are spread across administration screens. Your documentation may have the user’s name and the laptop’s serial number, with little connecting them to the cloud environment your team supports.

Weavestream’s Microsoft 365 integration brings that context into client documentation. Users, mail-enabled groups, managed devices, and tenant information appear alongside the assets, credentials, articles, and relationships your technicians already use.

One Integration, Separate Customer Connections

You register one multi-tenant Entra app for your Weavestream installation, then connect each customer through an administrator’s consent. Each connected tenant maps to its own Weavestream company.

Scheduled syncs use the application’s identity. They do not depend on a technician remaining signed in, and Weavestream does not store a customer’s administrator password or a user refresh token for the integration.

The app registration and permissions need an initial setup. Weavestream includes a setup guide and Check setup to help identify missing permissions, expired secrets, and connection problems. The Microsoft 365 integration guide covers the full process.

More Context Around People and Devices

Mapped fields put familiar facts into your layouts: names, email addresses, job titles, departments, device models, serial numbers, and operating systems.

A separate Microsoft 365 section carries provider-specific detail:

  • Users: assigned licenses, mailbox and OneDrive usage, account status, administrative roles, and available sign-in and MFA information.
  • Devices: Intune compliance, encryption, ownership, storage, and last check-in where those details are available.
  • The tenant: purchased versus assigned licenses, subscription status, storage totals, Secure Score, MFA coverage, and available recent security alerts.

These are useful starting points for a review. A disabled account that still holds a license deserves a closer look; it is not an instruction to remove the license automatically. The integration documents what Microsoft reports, while your team decides what action is appropriate.

Domains Join the Same Monitoring View

Verified custom domains feed the company’s Domains monitoring. If a domain is already there, perhaps from Cloudflare or a manual entry, Weavestream matches it by name and adds the Microsoft details.

A newly discovered domain gets the default monitoring checks. Microsoft’s initial onmicrosoft.com domain and unverified domains are skipped. Domains removed from the tenant are flagged rather than deleted from the documentation.

That keeps cloud identity and domain records connected without creating a second list for technicians to maintain.

Know What the Data Can Tell You

Available information depends on the customer’s licenses and granted permissions. Some sign-in and MFA information needs Entra ID P1. Intune device resources need Intune access; unavailable resources are skipped with a warning while the remaining resources can sync.

Storage reports also lag behind current usage. The integration shows the reporting date, so a storage bar should be read as a dated report rather than a live measurement.

Microsoft may conceal names in usage reports, preventing storage figures from being matched to individual users. Weavestream offers an optional administrator action to change that setting. It affects reports across the customer’s tenant, requires explicit confirmation and reauthentication, and is audited. Leaving concealment enabled is supported. Normal syncs are read-only; they never make this change automatically.

Start With One Client

Connect a test customer, check its organization mapping, choose the destination layouts, and review a dry run before starting a real sync. Then open a few people, devices, and domains to confirm the result matches how your team works.

Explore Weavestream’s integrations or follow the Microsoft 365 setup guide. Weavestream is free, self-hosted, and open source.

02 / Keep reading

Latest from the blog