integration-patterns
Skill46 starsChanged 8 months agoMITView on GitHub
Power Platform integration patterns with Azure services. Use when: Service Bus, Azure Functions, webhook, event-driven, hybrid, on-premises gateway, VNet, integration pattern, Event Grid, Azure Relay, private endpoints, custom connectors to Azure.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- dynamics365ninja/d365fo-clitheir own version, first seen Oct 29, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dynamics365ninja/d365fo-cli★ 45same name
- IngAs8/ClaudeSkill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-uxSkill
- ai-builderSkill
- almSkill
- architectureSkill
- azure-openaiSkill
- business-process-flowsSkill
- canvas-appsSkill
- code-appsSkill
- code-reviewerSkill
- copilot-studioSkill
- custom-connectorsSkill
- dashboardsSkill
- data-migrationSkill
- dataverse-mcpSkill
- dataverseSkill
- dataverse-web-apiSkill
- devops-engineerSkill
- env-strategySkill
- governanceSkill
- licensingSkill
- m365-integrationSkill
- model-driven-appsSkill
- observabilitySkill
- pcfSkill
- perf-optimiseSkill
- platform-builderSkill
- pluginsSkill
- power-automateSkill
- power-biSkill
- power-pagesSkill
- power-platform-teamSkill
- project-managerSkill
- securitySkill
- solutions-architectSkill
- spec-driven-devSkill
- test-engineSkill
- testingSkill
- uat-coordinatorSkill
- web-resourcesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 58
No dead-letter handling on Service Bus (lost messages go unnoticed)
- Distinctive: line 62
No monitoring on integration points (failures go undetected)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Skill: Integration Patterns
When to Use
Trigger when designing integrations between Power Platform and Azure services — Service Bus messaging, Azure Functions for compute, Dataverse webhooks, Event Grid, on-premises gateway, VNet connectivity, or hybrid architectures.
Integration Pattern Overview
| Pattern | Direction | Coupling | Best For |
| Service Bus | Dataverse → Azure (async) | Loose | Reliable messaging, event distribution |
| Azure Functions | Bidirectional | Medium | Custom compute, API intermediary |
| Webhooks | Dataverse → External (sync/async) | Loose | Real-time push notifications |
| Event Grid | Azure → Power Platform | Loose | Azure event-driven triggers |
| On-premises gateway | Power Platform → On-prem | Tight | Legacy system access |
| VNet integration | Power Platform ↔ Azure VNet | Tight | Network-level security |
| Custom connectors | Power Platform → Any API | Medium | REST API integration |
⚠️ 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:
- Service Bus — Azure Service Bus integration, topic/queue patterns, Dataverse plugin to Service Bus, reliable messaging, dead-letter handling, session-aware processing
- Azure Functions — when to use Functions vs plugins vs flows, HTTP-triggered for Custom Connectors, Dataverse bindings, managed identity auth, cold start mitigation
- Webhooks & Events — Dataverse webhooks (real-time push), webhook registration via API, payload schema, retry behavior, Event Grid integration
- Hybrid Connectivity — on-premises data gateway, Azure VNet integration, private endpoints for Dataverse, Azure Relay, security considerations
Decision Table: Which Integration Pattern?
| Requirement | Pattern | Why |
| Reliable async messaging | Service Bus | Guaranteed delivery, dead-letter, retry |
| Real-time event notification | Webhook | Immediate push on data change |
| Custom compute (validation, transformation) | Azure Function | Serverless, scalable, any language |
| Legacy on-prem database access | On-prem gateway | Bridge to SQL, Oracle, SAP |
| Network-isolated Azure resources | VNet integration | Private endpoint access |
| Fan-out to multiple subscribers | Service Bus topics or Event Grid | One event, many consumers |
| Simple REST API call | Custom connector | Low-code, reusable |
| High-volume batch processing | Azure Function + Service Bus | Decouple producer from consumer |
Anti-Patterns
- Synchronous HTTP calls in Dataverse plugins to external APIs (2-minute timeout, blocks user)
- On-premises gateway for everything (single point of failure, bottleneck)
- No dead-letter handling on Service Bus (lost messages go unnoticed)
- Webhook without retry-aware endpoint (missed events)
- Azure Functions with long cold starts on critical paths (user-facing latency)
- Tight coupling between Dataverse and external systems (breaks when external system changes)
- No monitoring on integration points (failures go undetected)
- VNet integration without private endpoints (traffic still goes over public internet)
Related Skills
plugins— Dataverse plugins that trigger integrationspower-automate— Flow-based integrations with connectorsazure-openai— Azure Functions as AI intermediarycustom-connectors— Custom connector creation for APIssecurity— Authentication for external integrations
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
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.