How to test the inbound connection update

Hello ​@kparkinson 
Thank you for reaching out, and welcome to the Docusign Community! We appreciate your question and assure you that we are fully committed to providing you with the best service possible.

This service update applies to all production accounts in NA1, NA2, NA3, NA4, and EU1 and all demo accounts across all sites. 

Here's how to check what site/server your account is hosted on:

There are a few ways to get this information:

• Docusign Admin: Organization Accounts list.
• eSignature Admin > Apps and Keys page: Account Base URL.
• eSignature Admin: Plan and Billing page.
   

  For affected accounts ( NA1, NA2, NA3, NA4, and EU1 and all demo accounts across all sites) please connect with your Network Administrator or IT department to confirm the following:

• If you restrict 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.

• Note: Inbound connections are primarily relevant if you're using the Docusign Connect-based Webhook, where DocuSign initiates calls to a webhook you provide  👉  Webhooks

  You only need to 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, if you are actively using Docusign Connect.

• If you restrict outbound connections to Docusign to specific subdomains, you must update your allow-list 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.

 👉  Have more questions about the transition, or wondering if you need to take action? Check out the FAQs.

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"

hi - I got that email already, and we made the changes requested, my question was how do we know that it all went through and will work?

Hello ​@kparkinson 
If you're wondering, ​​​​​​​how can we test the performance in the new environment before our production account is migrated?
We will be migrating Docusign Demo accounts first. We encourage you to utilize these Demo environments to test performance and address any concerns you may have before your production accounts migrate according to the schedule highlighted above. If you do not have access to a Demo account, you can self-provision one by going to developers.docusign.com. 
For your reference you may check this article: eSignature transactions will soon be processed in Microsoft Azure to better serve you.
 

Sincerely,

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

Hello ​@kparkinson 

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"