There’s a deadline coming in October 2026 that most GoDaddy email users haven’t heard about yet and honestly, that’s a problem.
Microsoft has officially confirmed that Exchange Web Services (EWS) will be blocked in Exchange Online starting October 1, 2026, with a full, permanent shutdown by April 1, 2027. No exceptions. No extensions.
If your email runs through GoDaddy’s hosted Microsoft 365 environment, this isn’t some distant IT concern. It’s a direct and urgent signal that your current setup is running out of road. Here’s what’s really happening, what’s at stake, and why the smartest thing you can do right now is migrate to a direct Microsoft 365 tenant before October arrives.
Exchange Web Services, or EWS, is a legacy API (Application Programming Interface) that Microsoft built roughly 20 years ago. It’s the behind-the-scenes protocol that many email platforms and integrations have used to connect apps to Exchange Online syncing calendars, pulling contacts, reading mailboxes, and handling other routine operations.
Here’s the thing: GoDaddy’s hosted Microsoft 365 environment has historically relied heavily on EWS-based architecture. When you manage Microsoft 365 through GoDaddy as a reseller, your tenant configuration, admin controls, and third-party integrations are tied to GoDaddy’s infrastructure layer. A large portion of that infrastructure depends on EWS to function.
So when Microsoft cuts the cord on EWS, GoDaddy-hosted tenants face a dual problem:
This isn’t a theoretical risk. Microsoft themselves have called out that even their own products Outlook, Teams, and Dynamics 365 needed to be updated to remove EWS dependencies. The API is genuinely going away, and GoDaddy’s managed environment has a larger exposure to this than most people realise.
Let’s be precise about the dates, because they matter:
October 1, 2026 — Microsoft begins disabling EWS globally across all Exchange Online tenants. Services and apps that rely on EWS will start failing. This is not a soft deprecation. It’s a hard block.
April 1, 2027 — EWS is fully and permanently disabled in Exchange Online. At this point, there is no re-enablement option. If you haven’t migrated by now, you’re looking at broken email workflows, failed integrations, and potential data access issues.
There is one small grace window worth knowing: organisations that configure an EWS app allow list and set EWS Enabled to True before the end of August 2026 will be temporarily excluded from the automatic October blocking. But that’s a workaround, not a solution. It only buys you a few extra months, and the final April 2027 deadline is absolute.
Realistically? If you’re still on GoDaddy’s managed M365 environment by August 2026, you’re already cutting it very close.
This is where it gets a bit specific to GoDaddy users, and it’s worth understanding clearly.
When Microsoft 365 is sold through GoDaddy as a reseller, your tenant is what’s called “federated” with GoDaddy. That means GoDaddy manages significant portions of your tenant configuration on your behalf. You don’t get full global admin access. You don’t control your own identity layer completely. And many backend operations that GoDaddy runs for you use EWS under the hood.
In a direct Microsoft 365 tenant — one you own and manage yourself, or through a certified Microsoft partner like Star Knowledge — you have full control over your environment. You’re not dependent on a third-party reseller’s backend processes staying functional. When Microsoft releases updates, deprecates APIs, or changes authentication standards, you can respond directly and on your own schedule.
GoDaddy has acknowledged the EWS change, but their reseller-managed setup creates an additional layer of complexity. As EWS gets disabled, the handshake between GoDaddy’s admin systems and your Microsoft 365 tenant becomes unreliable. Calendar sync, contact access, email routeing logic, and third-party app integrations all become vulnerable.
The cleaner, more permanent solution is to defederate from GoDaddy and migrate to a direct Microsoft 365 tenant before the October 2026 deadline.
If you’re thinking, “Maybe I can just wait and see,” here’s a practical look at what’s likely to break for GoDaddy-managed users who don’t act before October 2026:
Email integrations with CRM and business tools — Platforms like Salesforce, HubSpot, and older CRM systems that used EWS to sync contacts and calendar events will lose their connection to your mailbox.
Shared calendar and contact sync — Many organisations use EWS-based sync to keep shared calendars and public folders accessible across teams. This breaks completely when EWS is disabled.
Backup and archiving solutions — Legacy backup tools that used EWS to access Exchange Online mailboxes will stop functioning. This is a compliance risk for businesses that rely on automated email archiving.
Custom scripts and internal automation — If your IT team has built any PowerShell scripts or internal tools that call EWS to pull mailbox data, those scripts become dead code overnight.
GoDaddy’s own admin portal features – Certain account management and provisioning features in GoDaddy’s Microsoft 365 admin portal depend on EWS. As those features degrade, managing your users and licenses through GoDaddy becomes increasingly difficult.
The honest truth is that the full scope of impact varies by business. But the direction is clear: staying on GoDaddy’s managed M365 environment past October 2026 is a risk no business should take on unnecessarily.
The good news is that there is a clear, well-defined path forward. Here is how to approach it:
Step 1: Audit Your EWS Footprint
Sign in to the Microsoft 365 admin center and review the available usage and email app reports to identify applications that are currently using Exchange Web Services (EWS). You can also review EWS usage reporting in the Microsoft 365 admin center to identify services and applications that may depend on EWS.
If you are managing dozens of users through GoDaddy, several connected applications may be using EWS without being immediately visible to your team.
Step 2: Identify Migration Priorities
List every application and integration that depends on EWS in your environment and categorize them:
Microsoft first-party applications: Microsoft manages the transition for supported services as applicable.
Third-party applications: Check with each vendor regarding its Microsoft Graph API migration status and EWS support.
Custom scripts and internal tools: Review and, where necessary, rewrite integrations to use Microsoft Graph API.
GoDaddy-managed features: Identify services that need to be migrated or reconfigured outside the GoDaddy-managed Microsoft 365 environment.
Step 3: Plan Your GoDaddy Defederation and Microsoft 365 Migration
Defederation involves removing GoDaddy’s federation from your Microsoft 365 environment and transitioning authentication and tenant management to a Microsoft 365 environment that your organization directly controls.
A proper migration plan should cover:
Setting up or transitioning to a directly managed Microsoft 365 tenant with the appropriate licensing
Migrating email, contacts, calendars, and OneDrive data while maintaining data integrity
Reconfiguring DNS and MX records to point to the appropriate Microsoft 365 services
Reconnecting third-party applications and, where required, replacing EWS-based integrations with Microsoft Graph API
Providing user training and adoption support to minimize disruption
At Star Knowledge, our Microsoft 365 consultants support organizations with GoDaddy-to-Microsoft 365 migration and defederation projects using a structured migration approach.
Step 4: Start Planning Early
Do not wait until an EWS-related deadline is approaching before beginning your migration.
Migration projects of meaningful scale require planning, dependency analysis, testing, user communication, and cutover coordination. Starting early provides additional time to identify EWS dependencies, resolve compatibility issues, test the migration process, and complete the transition with less operational pressure.
A well-planned migration gives your organization time to validate the environment before the final cutover and address unexpected issues without relying on last-minute workarounds.
Working with us
Explore the top Microsoft 365 migration tools that help businesses move emails, files, and users securely with minimal downtime in 2026.
It’s easy to read a headline about a Microsoft deprecation deadline and feel like you’re being forced into something. But honestly, if you’re on GoDaddy’s managed Microsoft 365 today, this is a push towards something you’ll be glad you did.
Direct Microsoft 365 tenants – managed properly – give you capabilities that GoDaddy’s reseller model simply doesn’t offer.
Full admin control. You get complete access to the Microsoft 365 Admin Centre, Azure Active Directory (now called Entra ID), security and compliance centre, and every configuration setting Microsoft offers.
Advanced security features. Conditional Access policies, Microsoft Defender for Business, Privileged Identity Management, and proper multi-factor authentication enforcement are all available and configurable in a direct tenant.
Better licensing flexibility. You choose exactly which Microsoft 365 plans work for your business, without GoDaddy’s bundled and often limited plan structures.
Seamless Microsoft 365 Copilot compatibility. Copilot and AI-powered Microsoft features are built on modern Graph API architecture. A direct tenant ensures you’re positioned to take advantage of these tools as they evolve.
Future-proof infrastructure. Moving to Microsoft Graph API-based integrations now means you’re not chasing the next deprecation deadline. Graph API is Microsoft’s current and long-term standard.
Questions
Here’s what tends to happen with deadlines like this: Most organisations wait until Q3 2026 to start thinking about it seriously. Then every Microsoft partner, IT consultant, and migration specialist gets slammed with requests at the same time. Lead times stretch. Quality suffers. Businesses that could have had a smooth migration end up doing emergency cutover work under pressure.
You don’t need to be in that group.
If your email environment runs through GoDaddy’s managed Microsoft 365, the EWS deprecation is your strongest and most concrete reason to make the move to a direct Microsoft 365 tenant now. The technology is proven. The migration path is clear. And the benefits of a properly managed direct tenant extend well beyond just avoiding this one deadline.
Star Knowledge has been a Microsoft Partner since 2010. Our team of 30-plus certified Microsoft 365 consultants has completed over 300 migration projects, including dozens of GoDaddy defederation and migration projects specifically. We handle everything from the initial EWS audit through to post-migration support and user training.
If you want to understand exactly what your migration would look like — scope, timeline, and cost — get in touch with our team for a free consultation. The conversation takes 30 minutes. The peace of mind lasts a lot longer.
Keep reading