Docusign Integration with Dynamics 365 Roles Not working when assigned to Azure Security group

Question

Hello All,

Regarding Docusign for Dynamics 365, We recently migrated the Docusign Authentication Type from SOBO to OAuth2.0 for Production environment, however we noticed that earlier we had assigned Docusign related roles like Docusign User and Docusign Trace security roles to a azure Security group, and all the users who needed access to Docusign integration were added to that security group.

However, we noticed that this is not working anymore i.e. user is unable to see Sign with Docusign, send Signatures button and other Docusign functionalities on Opportunity when they are being assigned roles via Entra ID group or Team. However when roles are individually assigned, they are able to see.

Is this something due to the recent update that happened in Docusign?

If yes, then what are the options to be able to achieve this as there are about 60 users.

Noralynn.Niduaza · Answer

Hi ​@Priya,Thank you for engaging with the Docusign Community. We are pleased to have you here.We apologize for the issues you experienced with migrating to OAuth 2.0, and I’ll be glad to help you with this. I have reached out to our internal team to further investigate what could be the root cause of the issue you’re having. Please refer to the information below for your guidance:Why this is happening:Before displaying the Docusign buttons, the integration checks whether the current user has the required Docusign security roles. However, this check only detects roles assigned directly to a user — it does not detect roles inherited through an Azure Security Group. As a result, users in the Security Group appear to have no Docusign permissions, and the buttons are hidden.Why this wasn't an issue with SOBO:Under SOBO authentication, the button visibility did not depend on this role check in the same way. All Docusign operations were performed using a shared administrator account, so individual users didn't need to pass a per-user role validation to see and use the buttons. With OAuth, each user is validated individually, which is where this limitation surfaces.Workaround:Assign the Docusign User and Docusign Trace security roles directly to users who need access, rather than through the Azure Security Group.If the issue has not been resolved with the information provided, your best next step is to open a Support case so our tech team can take a closer look. 👉 Open a support caseBest regards,Noralynn | Docusign Community ModeratorFeel free to click the “Best Answer ✅” button below the post. That helps others in the Community find trusted answers faster.

Sign up

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Docusign Community

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.