Question about MS Approvals for Teams

Question

Question about MS Approvals for Teams

Jason Mudry 0

Is there a way to link MS Approvals for Teams to Consigno3?

I see links to Adobe Sign, DocuSign, Microsoft 365 eSignature, but we are mandated to use Consigno3 for some documents so would like to know if it is possible to link to that software platform as well?

0 comments

2 answers

Your answer

Answer 1

Good day Jason,

Unfortunately, Consigno3 isn't available as a built-in eSignature provider in Teams Approvals, so it cannot be selected the same way as Adobe Acrobat Sign, DocuSign, or Microsoft 365 eSignature.

If Consigno3 provides API access, your organization can integrate it through Power Automate:

1/ Confirm API availability with your Consigno3 administrator or vendor.

2/ Create a custom connector in Power Automate.

3/ Build a flow that sends documents or signature requests to Consigno3.

4/ Add a Teams approval step to manage the review process in Approvals.

5/ Configure status updates or notifications when signing is completed.

If custom development is available, your development team can also use Microsoft Graph approval APIs together with the Consigno3 API to build a tailored workflow.

If API integration isn't available, you can upload the document to Consigno3, create a Teams approval request, include the Consigno3 link in the approval details, ask approvers to complete the signing process in Consigno3, and then update the approval result in Teams.

Additional information is available in the following resources:

Create a custom connector for an approval flow - Power Automate | Microsoft Learn

Customize Approvals - Power Automate | Microsoft Learn

Approvals app APIs - Microsoft Graph | Microsoft Learn

I completely understand how these limitations in Teams can feel disruptive. It’s not just about aesthetics; these differences can genuinely affect how smoothly you work and navigate your day.

As a forum user, I hope you understand that I don’t have the ability to modify or escalate product issues directly. However, I strongly recommend submitting your feedback through the Microsoft Teams · Community. This is the most effective way to ensure your voice reaches the product team and can be considered for future improvements.

Once you've submitted your feedback, feel free to share the link here in the comments. I’ll be happy to upvote it to help bring more visibility.

If you have any questions, please don’t hesitate to reach out at any time.

Thank you for your patience and understanding.

If you have any extra questions about this answer, please click "Comment".

Answer 2

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 Approve and Reject are 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