Summary

Completed

With the device-availability service now fully wired up, you can look back at each decision point and see how it adds up to one capability. You can take an external REST API with no built-in connector and turn it into something a flow, app, or Copilot Studio agent reaches securely. Its data arrives in exactly the shape your logic expects.

What you learned

• You create a custom connector from an existing API description by importing an OpenAPI definition or directly from an Azure service. A GitHub repository of sample connectors is also available as a starting point when no description exists yet.
• You match the connector's authentication type, no authentication, basic authentication, an API key, or OAuth 2.0 with Microsoft Entra ID, to how the backend service actually verifies callers, and you keep OAuth client secrets renewed so connections keep working.
• You apply policy templates to reshape requests and responses or route calls at runtime. You also use OpenAPI extensions such as x-ms-visibility and x-ms-summary to control what a flow builder sees at design time.
• You recognize when a transformation needs custom code instead of a codeless template. You then choose between inline connector code for lightweight, connector-specific logic and an Azure Function for heavier or reusable logic.

Learn more

• Custom connectors overview
• Create a custom connector from an OpenAPI definition
• Specify connection parameters
• Authenticate your API and connector with Microsoft Entra ID
• Policy overview
• Create a custom connector with an OpenAPI extension
• Use custom code in a custom connector