NetDocuments has announced a significant infrastructure change coming in mid-to-late May 2026. They’re moving from their current content delivery network (Akamai) to AWS CloudFront, and migrating their core backend servers into AWS at the same time.
When law firms hear “infrastructure migration” and “IP address changes,” it’s natural to wonder if something needs to be done on your end. For the vast majority of NetDocuments law firm clients — especially those in the 10 to 150 user range — the answer is no.
Here’s what’s happening and why it’s not something you need to lose sleep over.
What’s Actually Changing
NetDocuments is making two changes in sequence:
Phase One (mid-to-late May): The content delivery network switches from Akamai to AWS CloudFront. This is the layer of the internet that routes your traffic to NetDocuments. For most users, this change will be completely invisible. You’ll open ndOffice, connect to NetDocuments, and nothing will feel different.
Phase Two (late May to early June, staggered by region): The NetDocuments backend servers move into AWS. This one comes with a planned maintenance window that includes actual downtime — likely more than 30 minutes but less than two hours. NetDocuments will post the specific window at least ten days in advance on their trust site.
Who Needs to Take Action
The firms that need to prepare are those with IT-managed firewall rules that control traffic by specific IP address. This typically means:
- Private FlexStore connections
- On-premises Exchange servers running ndMail
- On-premises ADFS for single sign-on
- Spam filters using NetDocuments IP allow lists
If any of those apply, your IT team will need to add the new AWS IP ranges before the cutover and leave the old ones in place until NetDocuments gives the all-clear after the maintenance window.
NetDocuments has already begun reaching out directly to firms they know are configured this way.
Why Most Law Firms Don’t Need to Worry
If your firm uses standard DNS to connect to NetDocuments — which is the default for virtually every cloud-hosted law firm — the changes are transparent. You’re not filtering traffic by IP address. You’re not running on-premises infrastructure that NetDocuments needs to access. Your cloud-hosted identity provider (Azure AD, Okta) doesn’t restrict who can fetch its metadata.
SSO through Azure AD or Okta? Not affected. Standard email delivery? Not affected. ndOffice, ndMail, ndMirror, ndSync? All continue to work through the same URLs — those aren’t changing.
The nature of this change, as NetDocuments puts it, is that firms are either not affected at all or significantly affected. There’s not much in between. And for the typical law firm Optiable works with, you’re in the first group.
What You Should Do
Honestly? Not much. Keep an eye on the NetDocuments trust site for the official maintenance window announcements. If you have an IT team or MSP managing your network, forward this post to them and ask whether they have any IP-based firewall rules for NetDocuments traffic. If they say no, you’re done
For further information, see this NetDocuments link.