Entry: Business configuration > Integrations. This is readiness guidance, not an installer or active marketplace.
avowr has REST endpoints for records and related operations. Authorised clients must use the supported identity, organisation scope, field validation and workflow actions. In the current Entra implementation, delegated user access is supported; an unattended app-only connector is not established merely by issuing client credentials. File transfer and workflow transitions use their own routes.
Before connecting a source, agree ownership, read/write direction, field mapping, stable source identifiers, duplicate handling, reconciliation and retry behaviour. Start with read-only access and a bounded local test. A read-only source extraction does not authorise changes in that source. Verify both allowed and denied records before enabling scheduled exchange.
The former MCP prototype accessed the database directly and did not preserve the application's user scopes. It is now disabled in every environment, with no bypass flag. Existing REST APIs are unaffected. A future MCP adapter must call the authorised APIs, preserve the requesting user's scope, limit exposed tools and obtain explicit confirmation for consequential writes. MCP is a protocol; installing a server does not make its tools trustworthy. There is no active connector marketplace or automatic credential provisioning through this page.
Complete when: The integration has an approved source/mapping, bounded permissions and tested failure/reconciliation behaviour. Do not share tokens, database credentials or unrestricted operator access with an agent.