Hello Ins1993,

Thank you for reaching out and the question.

If you restrict inbound network connections and allow-list specific Docusign IP addresses, you must update your allow-list to include all current Docusign IP ranges from our Trust Center by December 31, 2025, for both production and demo accounts. Please note: If your account is in AU, CA, or JP1, no action is needed on your production account, but action is needed on your demo account.

○ If you restrict outbound connections to Docusign to specific sub-domains, you must update your
allowlist to include the additional domains for your site.
■ demo-b.docusign.net
■ na1-b.docusign.net
■ na2-b.docusign.net
■ na3-b.docusign.net
■ na4-b.docusign.net
■ eu-b.docusign.net

○ No action is required if:
■ You do not use IP or domain allow-listing and you already allow-list the full IP ranges published on our Trust Center, or
■ Your production account is in AU, CA, or JP1 (action still needed on your demo account)

I hope this answers your question or concern, please feel free to let us know if you have additional questions.
 

Regards,

Raymond Hui

Docusign Customer Support

Hi ​@lns1993 

How are you? I'm checking in to see if you still need assistance. If yes, kindly reply here with more context or confirm if the issue has been resolved. 

If you run into any problems, we're happy to help with those here. Wishing you a smooth rest of your day!

Sincerely,

Ma. Cassandra | Docusign Community Moderator

If this helped, feel free to Like👍and click "Best Answer"

Hi, we also received the mail about demo-b.docusign.net etc.

We are using these Urls to connect to DocuSign services:

Production:
"DocuSignApi": { "AuthServer": "account.docusign.com", "AppUri": "https://apps.docusign.com", "AccountBaseUri": "https://eu.docusign.net" }

Development:
"DocuSignApi": { "AuthServer": "account-d.docusign.com", "AppUri": "https://apps-d.docusign.com", "AccountBaseUri": "https://demo.docusign.net" }

The frontend downloads scripts from 'https://js-d.docusign.com/bundle.js' and ‘https://js.docusign.com/bundle.js' and uses CSP like this:

<add name="Content-Security-Policy" value="default-src 'self';script-src 'self' 'unsafe-eval' 'unsafe-inline' https://docucdn-a.akamaihd.net https://*.docusign.net https://*.docusign.com;connect-src 'self' https://*.docusign.net https://*.docusign.com;frame-src 'self' https://*.docusign.net https://*.docusign.com;img-src 'self' data: blob: https://*.docusign.net https://*.docusign.com;style-src 'self' 'unsafe-inline';object-src 'none';" />

Since these connections are up and running and the addresses we are using are not mentioned in the Azure Transition Mail, should we be good to go?

Thanks,
Tim

Hello ​@timvdh 
You’re right, if that’s the case, no action needs to be taken, and you're good to go.

If you found the response to be a useful solution to your question, please “like” and mark it as the best answer by clicking “Select as Best” to make it easier for other users to find. Thank you!

Sincerely,

Ma. Cassandra | Docusign Community Moderator
If this helped, feel free to Like👍and click "Best Answer"

Hello ​@timvdh 

How are you? I'm checking in to see if you still need assistance. If yes, kindly reply here with more context or confirm if the issue has been resolved. 

If you run into any problems, we're happy to help with those here. Wishing you a smooth rest of your day!

If you found the response to be a useful solution to your question, please “like” and mark it as the best answer by clicking “Select as Best” to make it easier for other users to find. Thank you!

Sincerely,

Ma. Cassandra | Docusign Community Moderator

If this helped, feel free to Like👍and click "Best Answer"