Adobe Sign vs Adobe DC

[KevinB_GGW]

The Adobe Sign connector will be of great help in solving an issue with signing and managing policy documents.  

My organization has an Adobe DC for Teams license, but when I try to create an Adobe Sign connection and sign in using my Adobe ID, the create connection process doesn't finish.  I talked to Adobe, and they said that "Fill and Sign" within Adobe DC is the same functionality as the standalone Adobe Sign web service.

Does the Adobe Sign connector only work with the web service? 

[KevinB_GGW]

Have spent more time experimenting with Adobe DC, and it is clear that the e-signature functionality is using Adobe Sign.  

So my issue appears to be an issue with validating credentials.

Any help would be much appreciated

[v-bacao-msft]

Hi @KevinB_GGW,

I am afraid I can't reproduce your issue because I don't have an Adobe DC for Teams license.

But I created the Adobe Sign connection by using the free trial account registered on the Adobe sign website.

https://acrobat.adobe.com/us/en/sign.html

Image reference:

For more details on the Adobe Sign connector, please refer to link:

https://docs.microsoft.com/en-us/connectors/adobesign/

Best Regards,

Barry

[KevinB_GGW]

Thanks, Barry.  

I'll try to create a free account and see if that works, but it is important that I be able to do it from our Adobe for Teams environment.

I guess I'll have to put in a support ticket if I still have problems.

Keving

[KevinB_GGW]

I created a free account and it worked.  But when I deleted the connector and attempted to create the connector again, the sign-in process during the connector creation dialogue behaved as it had with my existing Adobe account, that is, instead of completing the action, it simply logged into my Adobe account.

Thanks

[v-bacao-msft · Accepted solution]

Hi @KevinB_GGW,

I also encountered this problem when I first tested it, but after many attempts, it will jump to the correct authorization interface and complete the action.

I think this is a problem with the redirect URL setting of the Adobe Sign connector. It should be a jump to the authorization interface, not the home page.

Best Regards,

Barry

[KevinB_GGW]

It worked when I just tried it.  Thanks!

[Anonymous]

I'm having the same problem. Each time I try to sign in, and enter my credentials, it takes me to the Adobe Sign web page, which then doesn't fix the connection. 

It appears from this solution that i'm just supposed to "keep trying?" That doesn't seem like a solution to me.

[rjhale]

Agreed.  That's certainly not a solution. 

I'm experiencing the same problem where the enterprise sign in simply redirects me to Adobe Sign, but the Flow connection is never fully established.  If I close the window, the Flow never establishes the connection. 

Any help getting this resolved would be much appreciated.  Thanks. 

[SteffenH]

Has there been a solution to this yet? i can't get it to work. My free trial works fine, but when using the account for produciton and after paying.....it just spins. 

[KevinB_GGW]

After a very frustrating time navigating all of this (without a ton of help from MS or Adobe), we learned that the only Sign license that supports the Flow integration is the Adobe Sign for Enterprise license.    It is actually in the fine print of the documentation, but we only figured it out after purchasing the Adobe Sign for Teams license.  

We went ahead and purhased the enterprise license for a single user, and I have successfully created the flow; it works like a charm

[JeffreyS]

@KevinB_GGW When you say need an enterprise license, do you mean Office 365 (E3 etc) or Adobe?  I have been trying to get my 365 small business account and Adobe DC pro with esign to work together to find this deal breaking info. 😞

[KevinB_GGW]

Sorry just seeing this.  You need an Adobe Sign Enterprise license

[vanderben]

I believe that your issue is because according to this you need an Adobe Sign for enterprise plan, which is one step up from Adobe Document Cloud for Teams subscription. The main difference is that it gives you access to APIs, which is used for the Power Automate connector.