Dear Adobe Support Community Wizzards
We're currently navigating through a perplexing technical challenge and could use the collective wisdom of the Adobe community and support to overcome it.
Issue at Hand: Attempting to leverage the Fill & Sign function within the Adobe Acrobat App in Microsoft Teams while logged in with a Federated ID is met with a relentless Access Denied Error. Intriguingly, this phenomenon exclusively manifests within the Adobe Acrobat App in Microsoft Teams, as the Fill & Sign function works harmoniously when using the Adobe Acrobat Reader desktop application with the same Federated ID.
Printscreen of the Error inside the MS Teams Adobe Acrobat App:
Adobe Acrobat Teams App Version:
Tech Speak: Our diagnostics thus far indicate that the issue lies within the integration of the Fill & Sign functionality in Microsoft Teams, particularly for users operating with Federated IDs. It appears to be an elusive hiccup that eludes conventional troubleshooting.
Also, when using a personal Adobe ID instead of the Federated ID the issue does not occur and the fill and sign function works properly within the MS Teams Adobe Acrobat App. Weird, right?
Current Support Journey: We've embarked on a journey with Adobe Support through the usual support ticket channels, and our case has been gracefully passed along to our account manager, "Software One." Despite these valiant efforts and several escalations, we find ourselves at an impasse.
Community Call to Action: In the spirit of collaborative debugging, we reach out to the Adobe community and support wizards for insights, solutions, or perhaps a sprinkle of magical debugging dust. If anyone has encountered and conquered a similar challenge or possesses arcane knowledge related to this issue, your guidance would be invaluable.
Thank you very much!
Luca
AdChoices