Custom Connectors for Power Platform and Copilot Studio
Custom Connectors for Power Platform and Copilot Studio wraps a REST API in a reusable, secure connector your makers and agents can call from Power Automate, Power Apps, and Copilot Studio — authentication setup (OAuth 2.0, API key, or basic), action and trigger definitions, documentation, and solution-based deployment into your environment. One connector per engagement, $1,950 fixed, delivered in about 5 business days once we have API documentation and test credentials.
What this engagement is
The Power Platform ships with hundreds of first-party connectors — we publish integration services across Asana, Mailchimp, Salesforce, HubSpot, and Zoho CRM precisely because those connectors exist. But sooner or later you hit a system that has an API and no connector: an industry-specific SaaS, an internal line-of-business service, a vendor who only gives you a REST endpoint and a PDF. The workaround most teams fall into is scattering raw HTTP calls and copied API keys across dozens of flows — fragile, insecure, and unmaintainable. A custom connector fixes that once. We define the API's operations in an OpenAPI definition, configure authentication properly (OAuth 2.0 including Microsoft Entra ID, API key, or basic auth — with secrets held in platform connections, never pasted into flows), add triggers where the API supports them, and deploy the connector as a solution into your environment. From then on, every maker sees your system as a first-class connector: point, click, connect. The same connector is also an AI investment. Copilot Studio agents consume Power Platform connectors as tools, so the connector that powers your flows and apps today is exactly how an agent reads and writes that system tomorrow — one integration surface, three products. If the goal is an agent, we demonstrate the connector as a Copilot Studio tool before handoff.
Success criteria
What you receive
How the work unfolds
Day 1: API review and scope agreement — we read the API documentation, verify the auth model with your test credentials, surface rate limits and quirks, and agree the action set in writing.
Days 1–2: Definition build — OpenAPI operations, parameters, and response schemas for the agreed actions.
Days 2–3: Authentication and policies — configure the security definition, create and test connections, add request/response policies where needed.
Day 3: Triggers — webhook registration or polling triggers where supported and scoped.
Day 4: Testing — every action against the live API, including failure paths, throttling behavior, and pagination where relevant; results documented.
Day 5: Deployment and handoff — solution import into your environment, end-to-end demonstration in a flow (and as a Copilot Studio tool where scoped), documentation walkthrough.
Prerequisites
Who does what
IT Partner
- Day-one API feasibility review and written scope agreement.
- Connector build: OpenAPI definition, actions, triggers, and policies.
- Authentication configuration and connection testing.
- Testing against the live API with documented results.
- Solution packaging, deployment to your environment, and the end-to-end demonstration.
- Maker documentation and handoff.
Your team
- Provide API documentation, sandbox credentials, and OAuth app registration with the API provider where required.
- Provide Power Platform environment access and approve our time-bound access request.
- Confirm the users of the connector hold the required premium licensing (we will flag the gap if they don't).
- Make the API contact available for questions during the engagement week.
- Test the demonstrated actions against your real scenarios and approve delivery.
- Own the vendor relationship and any API-side changes after handoff.
What's not included
Limitations & technical notes
Frequently asked questions
What is a custom connector?
A custom connector is a reusable wrapper that teaches the Power Platform how to talk to an API it doesn't natively support: which operations exist, what parameters they take, and how authentication works. Once built, your system shows up alongside Microsoft's first-party connectors in Power Automate, Power Apps, and Copilot Studio — makers pick actions from a list instead of hand-crafting HTTP requests.
When do we need one?
When a system you rely on has an API but no first-party or certified connector in the Power Platform catalog — common with industry-specific SaaS, internal services, and smaller vendors. Part of the day-one review is checking the existing connector catalog first: if a usable connector already exists, we tell you and you don't pay us to rebuild it.
Can Copilot Studio agents really use it?
Yes. Copilot Studio agents use Power Platform connectors as tools — an agent can call the connector's actions to read from or write to the wrapped system during a conversation or an automated run. If your goal is an agent, we scope the demonstration as a Copilot Studio tool, so you see the agent calling your API before handoff. Building the full agent itself is our Copilot Studio agent development service.
What licenses do our users need?
Custom connectors are a premium capability: makers and users generally need premium licensing in Power Apps or Power Automate (for example Power Apps Premium or a Power Automate premium plan), and Copilot Studio has its own licensing model. We confirm the licensing picture during the feasibility review so there are no surprises after delivery, and license costs themselves are billed by Microsoft, not part of our fee.
What kinds of APIs can you wrap?
REST APIs over HTTPS with JSON payloads are the sweet spot, whether cloud or on-premises through a supported gateway path. The API needs documentation, reachable endpoints, and an auth model the platform supports — OAuth 2.0 (including Microsoft Entra ID), API key, or basic auth. SOAP and RPC-style APIs, and APIs with exotic authentication, get an honest case-by-case answer in the feasibility review.
What exactly does the $1,950 fixed price cover?
One connector for one API: the feasibility review, the action set agreed on day one, authentication setup, triggers where supported and scoped, testing with documented results, solution deployment, a working demonstration, and maker documentation. Each additional API is its own engagement at the same price. Building full flows, apps, or agents on top of the connector is scoped separately.
Does the connector support triggers, or only actions?
Both, when the API allows it. If the API supports webhook subscriptions, we build push-style triggers ('when a record is created…'); if it only supports reads, we can build polling triggers. Some APIs offer no workable trigger pattern, in which case we say so on day one and design around it with scheduled flows.
How is authentication and secret handling done?
The connector carries a proper security definition — OAuth 2.0, API key, or basic auth — and credentials live in platform connections, which are stored and managed by Microsoft's connection infrastructure, not pasted into individual flows or apps. Each user or service account gets its own connection, and access to shared connections is controlled by your environment's policies.
Where does the connector live, and who owns it?
It is deployed into your Power Platform environment inside a solution, and you receive the solution files. It is your asset in your tenant — nothing routes through IT Partner infrastructure, and no ongoing relationship with us is required to keep using it.
How long does it take?
About 5 business days from the moment we have API documentation and working test credentials. The single most common delay is waiting on the API vendor for sandbox credentials or an OAuth app registration — so we ask for those before the clock starts.
What happens if the vendor changes their API later?
Connectors break when the API underneath them changes — that is true for Microsoft's own connectors too. You own the connector and can update it, or we can update it for you as a separate piece of work. If you expect frequent API changes, tell us in the review and we can talk about an ongoing arrangement.
Can you also build the flows, apps, or agents that will use the connector?
Yes — that is much of what we do. The connector engagement ends with a working demonstration; full automation builds are covered by our Power Platform integration and business process automation services, and agent builds by our Copilot Studio agent development service. Keeping the connector as its own fixed-price unit keeps each engagement's scope clean.
How do we pay?
The price is $1,950 fixed, stated in writing before work begins — and you pay after you approve delivery. If the day-one feasibility review finds the API can't be wrapped as planned, we tell you then and adjust scope together, before build effort is spent.