>

DocuSign Migration to Azure Email

Answered
Mike Schepker

City of Prince George
US/Canada
25.2

Customer received the following email from DocuSign about changes to DocuSign. Is there anything we need to do on our end? Dustin said that he also received the email and DevOps would need to determine if we need to make changes: 

Thank you for being a valued Docusign customer! We have two important updates to share regarding your eSignature service. As a key step in enhancing our cloud infrastructure, your transactions will be migrating to Microsoft Azure. We appreciate your trust in our service and are dedicated to ensuring this transition is smooth and that your data remains secure.

1. Service Update: Transaction Processing in Microsoft Azure cloud

As part of our commitment and ongoing investments to provide the most secure and reliable services, we’re migrating Docusign eSignature transaction processing from our on-premise infrastructure to Microsoft Azure. 
 
 

  • What: 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.
  • When: Migration will occur in September 2025 for demo accounts, and between November 2025 and May 2026 for production accounts.
  • Your Experience: There should be no change to your Docusign interface and how you use our service.

Migrating to Microsoft Azure is a key infrastructure update that allows us to better serve you. The benefits include:
 

  • Better demand management: The elastic nature of the cloud allows us to better respond to spikes in demand, ensuring that our services and your business continues to operate smoothly even during peak demand periods.
  • A more agile and resilient system: The cloud allows us to build a more agile system that can quickly respond to changing enterprise infrastructure demands and deploy across multiple locations, leading to higher resiliency and fewer disruptions to your service.
  • Faster innovation: Azure's flexibility and scalability allow us to channel resources into rapid innovation, enhancing your experience and enabling us to deliver powerful solutions that solve your agreement challenges.
  • Robust security: Migrating to Azure will preserve your current security posture and lay the groundwork that will enable us to deliver additional security enhancements in the future.

2. Action Needed (For subset of Customers): Review Your IP Address & Domain Allow-Listing Settings

To ensure continuous functionality of your Docusign experience, including your integrations and signing processes, please confirm if your network settings utilize IP or domain-based allow-listing. This will allow us to ensure everything continues to run smoothly during our upcoming service update.
 
 

  • What action is required? Please contact your Network Administrator or IT department to confirm the following:
     
    • 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 Centerby 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)

Questions? Please visit the Docusign Trust Center for IP details or read our FAQs for more information. If you have questions, create a post in the Docusign Community and our team will get back to you. 

We appreciate your trust in us as we aim to offer you these key service enhancements with an uncompromising level of security, safety and reliability expected of your Docusign eSignature service.


Sincerely, 
The Docusign Team

cc Cathy Herrick Richard Marmura 

Comments

7 comments

Date Votes
  • Seth Halvaksz

    I messaged Kyle LeMarbe to ask what we'd need to do

  • Mike Schepker

    Thanks Seth Halvaksz !

  • Seth Halvaksz

    Kyle told me the cloud architecture team is going to review this.  I can't tag hm in this post, so will update here when i hear back.

  • Mike Schepker

    Hi Seth Halvaksz have you heard anything back from Kyle or the Cloud Architecture team on this? Thanks!

  • Seth Halvaksz

    I have not, i'll follow-up again

  • Seth Halvaksz

    Just received this from Kyle:

    “The ticket is in the current sprint but has not been worked yet.  https://ungerboeck.atlassian.net/browse/ISH-4591”

  • Seth Halvaksz

    Providing an update. The ticket ISH-4591 was completed. There is nothing found to be needed here.

    Tim Crank

    September 5, 2025 at 12:53 PM

    I can find no evidence of ACLs setup in Enterprise cloud that limits access for DocuSign, therefore no work is necessary for this issue.

    Note that I did send a Teams message to Jayme Bochman, just to make sure they are aware of this. I don’t know if Internal does anything with DocuSign or if they are already aware of these changes…it was sent just as a heads-up.

Please sign in to leave a comment.

Didn't find what you were looking for?

New post