Skip to main content

To better support your needs and stay ahead of what’s next, Docusign eSignature is moving to the cloud—bringing more agility, security, and speed to every transaction.

Over the next several months, all Docusign eSignature transactions will move to Microsoft Azure. This shift is aimed at giving you stronger security, better performance, and faster innovation.

This update applies to all production accounts, except those hosted on AU, CA, and JP1 servers, which already operate on Azure. This also applies to all demo accounts. The transition will begin in September 2025 for demo accounts and roll out to production accounts from November 2025 to May 2026.

✨ Key takeaways:

  • Robust security: Your data gets top-tier protection with Azure's trusted infrastructure.

  • More agility and resilience: A cloud-native infrastructure means faster response to change, improved uptime, and fewer disruptions.

  • More innovation, faster: With Azure, we can build and ship features more quickly to address your biggest agreement challenges. 

  • Better demand management: Azure’s elastic cloud helps us scale to meet spikes in demand so your agreements stay on track even during peak periods. 

✅ Action needed (for a subset of customers): Review your IP address & domain allow-listing settings

If your organization restricts inbound network connections and allow-lists specific Docusign IP addresses, you’ll need to update your allow-list to include all current Docusign IP ranges. This ensures your integrations and signing processes continue running smoothly.

  • IP allow-listing: Ensure your allow-list includes all current Docusign IP ranges from our Trust Center by December 31, 2025 for both production and demo accounts.

    • Note: If your production account is in AU, CA, or JP1, no action is required for production, but action is needed for demo accounts.

  • Domain allow-listing: Update your settings to include the following sub-domains:

    • 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 don’t use IP or domain allow-listing, or

  • You already allow the full IP ranges published on our Trust Center, and

  • Your production account is in AU, CA, or JP1 (demo accounts still need updates).

👉 Curious about the transition or wondering if you need to take action? Drop your questions in the comments section below or check out the FAQs.

I believe one of the bigger ‘integration’ challenges parties will face will be on the DocuSign Connect callback interface, where a list of IP addresses trusting the inbound callback POST may be configured.  In our case, this is an Azure function app that receives the REST POST JSON.


We need to have the customers who have integrated with Docusign's eSignature update the IP whitelist in their firewalls.

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟The only DocuSign Partner globally with two Certified eSignature Technical Consultants

🏆 DocuSign 2025 APAC Growth  Engine Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedInhttps://www.linkedin.com/in/gehengfeng

📬 For business inquiries, feel free to connect via :

WeChat/微信: +86 1381880287

WhatsApp: +65 97796938


Reply