Additional task-related features and issues within Microsoft Teams for business
Consigno3 cannot currently be selected as a native e-signature provider in Microsoft Teams Approvals, but it can potentially be connected through Power Automate if Consigno3 exposes a suitable API.
Microsoft’s native integrations are limited to Adobe Acrobat Sign, DocuSign eSignature, and Microsoft 365 eSignature; the Teams admin settings likewise expose only Adobe Sign and DocuSign as third-party provider toggles.^1^^2^
Conditional integration through Power Automate
First, ask the Consigno3 vendor or administrator whether your deployment provides:
- A REST API or OpenAPI definition
- Authentication credentials supported by Power Automate
- Operations to submit a document, specify signers, retrieve signing status, and download the signed document
- A webhook or status endpoint for detecting completion
If those capabilities are available:
- Sign in to Power Automate.
- Go to Data → Custom connectors.
- Select New custom connector → Create from blank.
- Enter the Consigno3 API host.
- Under Security, configure the authentication method required by Consigno3.
- Under Definition, add the required triggers and actions—for example:
- Submit document for signature
- Get signature-request status
- Download completed document
- Cancel a request
- Create an Automated cloud flow using the custom connector.
- Add Start and wait for an approval if an internal Teams approval must occur before sending the document to Consigno3.
- Add a condition for the Teams response. The values
ApproveandRejectare case-sensitive. - In the approved branch, call the Consigno3 action that submits the document. Use a webhook or polling trigger to detect completion and then store the signed document in the required repository.
Microsoft documents this custom-connector pattern specifically for connecting Teams Approvals to line-of-business applications.^3^
Important distinction
This creates a custom workflow involving Teams Approvals and Consigno3. It does not add Consigno3 to the native provider list shown when a user creates an e-signature request directly in the Approvals app.
If a deeper custom application is required, the Microsoft Graph Approvals APIs can create, update, and list approval items, assign approvers, and notify users in Teams.^4^ Consigno3 would still need an accessible integration interface; Graph handles the Teams approval objects, not the signing operation inside Consigno3.
If Consigno3 does not expose an API, webhook, or supported automation interface, there is no documented direct integration path. The practical fallback is to run the Consigno3 signing process separately and use Teams Approvals only for the internal approval or tracking stage.
Before implementation, have the Microsoft 365/Power Platform administrator verify licensing, data-loss-prevention policies, credential handling, document-storage location, retention, and whether the workflow satisfies the mandate that these documents be signed through Consigno3.
References