How-to guides for governing Microsoft 365 and every AI tool
Each guide takes one governance job, from shadow AI to DORA evidence, and breaks it into steps you can run on your own estate.

AI tools and agents
8 guidesFind every assistant and agent, give each one an owner, and review what it can reach.

How to govern SharePoint agents
A SharePoint agent is only as safe as the site it reads. Inventory the agents, fix labels and sharing on their sites, and give each an owner. Read the guide
How to govern ChatGPT Enterprise and custom GPTs
Custom GPTs, projects and connectors multiply fast. Inventory them, see who each is shared with and join users to your Microsoft identity. Read the guide
How to govern Claude Enterprise usage and spend
Claude Enterprise spend and projects sit outside Microsoft 365. Join users to Entra ID, read spend by department and clean up stale projects. Read the guide
How to govern AI coding assistants
Coding assistants read source code and internal context. Inventory them, map their access, give each an owner and review it like any AI tool. Read the guide
How to control shadow AI
Find the AI tools nobody approved, assess what they can reach, and bring the useful ones under the same inventory, owners and reviews as the rest. Read the guide
How to inventory the AI tools in use across your organization
Build an inventory of the AI assistants and agents in use, with an owner, data reach and risk for each, starting in Microsoft 365 and extending out. Read the guide
How to govern Microsoft Copilot agents
Keep every Copilot Studio and SharePoint agent inventoried, owned and risk-ranked, so agent creation does not turn into sprawl and data exposure. Read the guide
How to govern AI tools beyond Microsoft Copilot
Apply one governance model to every AI tool your teams use: an owner, a risk rating, an access review and one report, joined to your Entra ID. Read the guideCopilot readiness
5 guidesGet permissions and content in shape before Copilot answers with them, then keep the seats you pay for in use.

How to apply sensitivity labels before a Copilot rollout
Copilot answers from whatever people can open. Find unlabeled teams and sites, get owners to label them, and prove the gap is closing. Read the guide
How to measure Microsoft 365 and Copilot adoption
Set an adoption baseline, measure real usage by service and department, and show which Microsoft 365 and Copilot seats pay off. Read the guide
How to reclaim unused Microsoft 365 Copilot licences
Copilot seats stay assigned until someone removes them. Define what used means, find idle seats by owner and department, notify, then reclaim. Read the guide
How to prepare Microsoft 365 for a Copilot rollout
Copilot answers with each user's permissions. Measure exposure, close oversharing, label sensitive sites, retire stale content, then pilot. Read the guide
How to detect and fix SharePoint oversharing
Find SharePoint content that more people can reach than intended, fix the most sensitive first, repair the causes and re-check on a cycle. Read the guideSprawl and ownership
12 guidesStop teams, apps and tenants multiplying without an owner or an end date.

How to make sure every Microsoft 365 workspace has an owner
Find the Teams, sites and groups with no owner, one owner or a leaver as owner, and keep every workspace accountable to a named person. Read the guide
How to automate the Microsoft 365 workspace lifecycle
Run every Teams team, site and group from request to archive, with owners deciding at each stage and the record kept. Read the guide
How to standardize Teams and SharePoint provisioning with templates
Let people request Teams and SharePoint sites from templates, with owner, naming, label and approval built in, so sprawl does not start. Read the guide
How to clean up inactive SharePoint sites
Find the SharePoint sites nobody uses, ask each owner, and archive or delete what is not needed, with the decision on record. Read the guide
How to stop unmanaged workspaces driving up Microsoft 365 costs
Unowned, unused Teams and SharePoint sites keep consuming storage and licences. Find them, give them an owner, and retire what nobody needs. Read the guide
How to reduce SharePoint storage costs
Find what fills your SharePoint and OneDrive storage, retire what nobody uses, and make owners answerable for the rest. Read the guide
How to find and reassign ownerless Power Apps and flows
Find Power Apps and Power Automate flows whose owner has left, then assign a new owner or retire them. Read the guide
How to govern Power BI workspaces and sharing
Put an owner on every Power BI workspace, find what is shared outside your organization and clear what nobody uses. Read the guide
How to segment a Microsoft 365 tenant by subsidiary, region or business unit
Segment one Microsoft 365 tenant by subsidiary, region or business unit so each admin sees only their part, without splitting into separate tenants. Read the guide
How to control Microsoft Teams sprawl
A repeatable routine for Teams sprawl: inventory every team, find inactive and ownerless ones, set owners and expiry, review, then archive with a trail. Read the guide
How to govern the Power Platform
Govern Power Apps, Power Automate and Power BI as one low-code estate: inventory it, give every asset an owner, watch connectors and review access. Read the guide
How tenant sprawl slows Microsoft 365 governance, and how to reverse it
Tenant sprawl turns governance into search and cleanup. Measure what it costs, then stop it at creation with owners, expiry and reviews. Read the guideVisibility and policy
5 guidesSee the whole estate in one place and turn business rules into policies that run on their own.

How to close governance blind spots across Microsoft 365 admin centers
Each Microsoft 365 admin center shows one service, so the gaps between them go unseen. One inventory, named owners and policy checks close them. Read the guide
How to monitor Microsoft 365 governance posture continuously
Governance posture is the current state of ownership, access and policy across Microsoft 365. Monitor it with an inventory, policy checks and a trend. Read the guide
How to align Microsoft 365 governance with business policies
Governance drifts from business policy when rules live in documents and the tenant runs on its own. Testable rules, owners and continuous checks close the gap. Read the guide
How to automate Microsoft 365 governance policies
Turn written rules into policies that check Microsoft 365 on every scan, then let automations fix what they find, with a person approving where it matters. Read the guide
How to add business metadata to Microsoft 365 workspaces
Put cost center, owner and project on every team and site, capture them at creation and keep them current, so policies follow your business. Read the guideAccess and data protection
7 guidesKeep access in line for guests, apps and leavers, review it on a fixed cycle, and watch the conditions around your data.

How to keep track of permissions across Microsoft 365
Permissions in Microsoft 365 spread across Teams, SharePoint, OneDrive and Entra ID. Inventory who can reach what, review with owners and keep the record. Read the guide
How to manage guest users across Microsoft 365
Manage guests from invitation to removal, with rules for who may invite them, who sponsors them, when access is reviewed and how it ends. Read the guide
How to review Entra ID app registrations and their permissions
Find every app registration in Entra ID, name an owner, check its permissions and secrets, and retire what nobody needs. Read the guide
How to offboard users in Microsoft 365 without losing data or control
Offboard a leaver without orphaned Teams, lost OneDrive files or paid-for licenses: transfer ownership first, then disable the account. Read the guide
How to keep data residency controls consistent in Microsoft 365
Microsoft Multi-Geo sets where data is stored, but consistency needs oversight. Inventory where workspaces and guests sit and check each against the residency rule. Read the guide
How to run recurring access reviews across Microsoft 365
Owner-led access reviews on a fixed cycle, across Microsoft 365 workspaces, so access stays in line and the proof is kept. Read the guide
How to monitor data loss prevention across Microsoft 365
DLP policies stop known patterns. Watch the conditions around them too: external sharing, mail redirect rules and connector use, ranked and fixed. Read the guideCompliance evidence
4 guidesTurn the EU AI Act, DORA and NIS2 into records an auditor can check.

How to reduce audit preparation effort in Microsoft 365
Audit preparation balloons when collaboration spaces have no owner and no record. Named owners, regular reviews and exportable reports shrink it to an export. Read the guide
How to build EU AI Act evidence across your AI tools
The EU AI Act applies to every AI system you use, whoever made it. Keep a record per system: purpose, data, owner, risk class and last review. Read the guide
How to produce DORA audit evidence in Microsoft 365
DORA counts the agents, flows and workspaces in your tenant as ICT assets. Inventory them, assign owners, review access and export the evidence. Read the guide
How to prepare Microsoft 365 for NIS2
NIS2 asks you to prove control, not assert it. Map the duties to Microsoft 365, set a baseline, keep owners and reviews current and package evidence. Read the guideNo guide matches that yet. Try a product name such as Teams or Copilot, or .
About these guides
Quick answers, kept in step with the guides on this page.
- Who writes the Rencore how-to guides?
- Torsten Mandelkow, Rencore co-founder, writes every guide on this page.
- What do the guides cover?
- 41 governance jobs across Microsoft 365 and the AI tools your teams use, in 6 groups: AI tools and agents, Copilot readiness, sprawl and ownership, visibility and policy, access and data protection, and compliance evidence.
- Where should I start?
- Start by finding out what you have with “How to inventory the AI tools in use across your organization”. Then close the exposure with “How to detect and fix SharePoint oversharing”, and keep it that way with “How to run recurring access reviews across Microsoft 365”.
- How often are new guides added?
- The newest guide, “How to add business metadata to Microsoft 365 workspaces”, was published on 11 November 2026. New guides appear at the top of their group with a “New” label.
Run these steps on your own estate
Rencore keeps the inventory, owners and access reviews these guides ask for in one place, starting with Microsoft 365 and Copilot.