We have published a new guide on Partner Central that will be useful for partners working with customers who want to control internet access on their Sage CRM servers.

The Sage CRM Internet Access Requirements Guide provides a clear, practical reference for understanding which outbound connections are required for Sage CRM to operate correctly, and which are optional depending on the features in use.

You can access the guide on Partner Central here:
https://partnercentral.sage.com/prm/api/objects/v1/asset/fvqx4xqbq8dx/_view

Why this guide matters

Many customers, particularly those in regulated industries or with mature IT security policies, want to minimise outbound internet connectivity from application servers. This often leads to questions during deployment such as:

• Which URLs and ports does Sage CRM actually need?

• Can we safely block general internet access?

• What is required for integrations such as Mailchimp or Microsoft Exchange Online?

• What changes if we are not using specific features?

Until now, this information has often been spread across the documentation, shared informally or reconstructed during security reviews. This guide brings everything together in one place.

What the guide covers

The guide explains Sage CRM connectivity requirements in a structured, feature-based way, including:

• Core internal services such as IIS and Tomcat, which do not require internet access

• Outbound SMTP requirements for sending email from Sage CRM

• Microsoft Graph endpoints required for Exchange Online synchronisation

• Mailchimp API access and domain allow listing

• Optional services such as online help, Sage CRM Ally and Labs Webhooks

• Licensing and update related connectivity

• Recommended minimal access configurations for locked-down environments

Each section makes it clear when access is required and when it can safely be disabled.

How partners can use the guide

For partners, the guide can be used as:

• A deployment checklist during new implementations

• Supporting documentation during customer security and firewall reviews

• A reference when responding to IT teams asking for precise URL and port details

• A way to clearly explain the impact of disabling specific features

It helps partners demonstrate that Sage CRM can operate securely with limited external connectivity.

How customer IT teams can benefit

For customer IT and security teams, the guide provides:

• Clear justification for each required outbound connection

• Confidence that unnecessary internet access can be blocked

• A shared reference that avoids repeated clarification during audits or reviews

• Alignment with common security principles, such as least privilege and network segmentation

This makes it easier to approve Sage CRM deployments in environments with strict security controls.

Feedback and next steps

This guide reflects current Sage CRM releases and commonly used integrations. As the platform evolves, particularly around cloud services and APIs, we will continue to update this guidance.

If you have feedback, edge cases or additional integrations you would like to see covered, please share them through your Sage contacts or partner channels.

We hope you find this guide a valuable addition to your Sage CRM implementation toolkit.