agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/m365-integration/SKILL.md

m365-integration

Skill46 starsChanged 8 months agoMITView on GitHub

Microsoft 365 integration with Power Platform. Use when: Teams, SharePoint, Graph API, Outlook, Microsoft 365, M365, Copilot connector, Teams tab, Adaptive Cards, SharePoint lists, Graph queries, email templates, calendar integration.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not handling Graph API pagination (missing data beyond first page)

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Microsoft 365 Integration

When to Use

Trigger when integrating Power Platform with Microsoft 365 services — embedding apps in Teams, connecting to SharePoint, using Microsoft Graph API, building Outlook integrations, or creating Teams bots via Copilot Studio.


Integration Surface

M365 ServicePower Platform Integration Points
TeamsCopilot Studio bots, embedded apps (tabs), Adaptive Cards from flows, Teams connector
SharePointLists as data source, document libraries, SharePoint-embedded forms, knowledge source for agents
Microsoft GraphGraph connector, custom connector, delegated/app permissions
OutlookEmail triggers/actions, calendar integration, shared mailboxes, room booking
OneDriveFile operations in flows, document storage for apps
PlannerTask creation/management from flows

⚠️ REQUIRED: Load Sub-Files Before Implementation

SKILL.md is a summary only — it is NOT sufficient for implementation.

The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:

  • Teams Integration — Copilot Studio bot deployment, Adaptive Cards from flows, Teams tab embedding (Canvas/Code Apps), Teams connector actions, deep linking, personal app vs channel tab
  • SharePoint Integration — SharePoint connector patterns, document library operations, list forms, migration from SP lists to Dataverse, when to use each
  • Microsoft Graph API — Graph connector, custom connector for Graph, delegated vs app permissions, common queries, pagination, batch requests
  • Outlook Integration — Outlook connector in flows, email templates with dynamic content, calendar integration, shared mailbox patterns, meeting scheduling

Anti-Patterns

  • Using SharePoint lists as primary database for apps with > 5000 items (delegation limits, performance)
  • Hard-coding SharePoint site URLs in flows (breaks across environments)
  • Using personal Graph permissions in production flows (use app permissions)
  • Embedding Canvas Apps in Teams without testing the Teams container (layout issues)
  • Sending emails from personal accounts in automated flows (use shared mailbox)
  • Not handling Graph API pagination (missing data beyond first page)
  • Creating Teams channels programmatically without governance (channel sprawl)
  • Using Outlook connector for bulk email (throttling, abuse detection)

Related Skills

  • copilot-studio — Teams bot deployment, agent channels
  • canvas-apps — Canvas App embedding and SharePoint integration
  • power-automate — Flow connectors for M365 services
  • custom-connectors — Custom Graph API connector creation
  • governance — DLP policies for M365 connectors

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.