Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Microsoft 365
Defines source-backed office productivity and collaboration, evidence handling, and action boundaries.
Read the fileOverview
Microsoft 365 overview
Use this bundle to structure office productivity and collaboration while keeping official-source context separate from account, organization, project, document, or environment evidence.
Read the fileWorkflow
Microsoft 365 source-backed triage
1. State the requested decision or deliverable. 2. Inventory evidence: tenant, subscription, and application scope, file, site, mailbox, team, or workspace identity, document version and.
Read the fileTemplate
Microsoft 365 work and governance brief
Review-ready brief for office productivity and collaboration, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Microsoft 365
- Teams working in Business services, Education, Public sector
When to use it
- A proposed Microsoft 365 configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Prepare a microsoft 365 work and governance brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce review-ready decisions with explicit verification and approval boundaries.
What it helps produce
- Microsoft 365 work and governance brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Microsoft 365 and produce Microsoft 365 work and governance brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with Microsoft Learn — Microsoft 365, then confirm that the reference is current and applicable. Inspect Microsoft 365 before drafting.
Context path: bundles/tools/microsoft-365
What the bundle includes
Tools
- Microsoft 365
Frameworks
- source-evidence matrix
- office-productivity-and-collaboration evidence matrix
- qualified-review gate
Evaluations
- Microsoft 365 source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Use official Microsoft 365 sources for general context; local office productivity and collaboration, configuration, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for tenant, subscription, and application scope, file, site, mailbox, team, or workspace identity, document version and content evidence, sharing, membership, and permission state, retention, sensitivity, compliance, and administrator policy, automation and integration configuration, and audit, approval, and source-of-record evidence.
- Do not infer tenant configuration, license, file state, permissions, sharing, retention, sensitivity labels, automation.
Safety notes
- Minimize personal, customer, employee, financial, credential, and other sensitive data.
- Require explicit confirmation before sending messages, sharing files, changing content, permissions, retention, labels, tenant settings, or automations.
- Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.