What Microsoft's OneDrive URL Change Means for Azure Virtual Desktop and Windows 365

Microsoft has announced a significant change to OneDrive URLs as part of its long-term strategy to unify Microsoft 365 cloud services under the cloud.microsoft domain.

While the change is designed to be seamless for most users, organisations running Azure Virtual Desktop (AVD), Windows 365, FSLogix, and custom Microsoft 365 integrations should understand the potential impact and review their environments before rollout begins.

📢 What's Changing?

Historically, OneDrive URLs have used SharePoint-based domains such as:

https://contoso-my.sharepoint.com

Microsoft is introducing a new unified URL format:

https://onedrive.cloud.microsoft

The rollout is expected to begin globally in July 2026 and continue through June 2027.

Importantly:

✅ Existing links continue to work

✅ Existing SharePoint URLs remain supported

✅ No user action is immediately required

🎯 Why Is Microsoft Making This Change?

Microsoft is gradually consolidating Microsoft 365 services under the cloud.microsoft domain.

Benefits include:

• Simplified user experience
• Consistent branding
• Reduced URL complexity
• Better alignment across Microsoft 365 services

📅 Rollout Timeline

Microsoft has confirmed that both URL formats will coexist indefinitely.

🖥️ What Happens for Users?

Users will begin seeing:

onedrive.cloud.microsoft

instead of:

contoso-my.sharepoint.com

when accessing their OneDrive content.

Example

Today

https://contoso-my.sharepoint.com

Future

https://onedrive.cloud.microsoft

The actual file access experience remains unchanged.

☁️ Impact on Azure Virtual Desktop

For most AVD users:

👉 There should be little to no user-facing impact.

However, AVD administrators should review several areas.

1. Conditional Access Policies

Many organisations have Conditional Access policies that target:

• SharePoint Online
• OneDrive
• Microsoft 365 services

Review:

• Named locations
• Session controls
• Network restrictions

to ensure no custom URL filtering assumptions exist.

2. Network Allow Lists

AVD environments commonly use:

• Azure Firewall
• Palo Alto
• Fortinet
• Zscaler
• Netskope

Review any rules referencing:

*.sharepoint.com

and prepare to include:

*.cloud.microsoft

where appropriate.

3. Secure Web Gateway Platforms

Customers using:

• Zscaler
• Netskope
• Prisma Access

should validate:

• URL categorisation
• SSL inspection policies
• Allow lists

before migration occurs.

💾 Impact on FSLogix

FSLogix itself is unlikely to be directly impacted because:

• Profile Containers remain unchanged
• ODFC Containers continue operating normally
• Authentication flows remain Microsoft 365 based

However:

Review ODFC Configurations

Organisations using:

• Outlook Cached Mode
• OneDrive synchronisation
• Office Containers

should validate:

• OneDrive sign-in behaviour
• Known Folder Move (KFM)
• User profile redirections

during testing.

🖥️ Impact on Windows 365

For Windows 365 Cloud PCs:

Impact should be minimal.

However administrators should review:

Network Policies

Ensure:

• Web filtering policies
• Corporate proxy configurations
• Cloud access controls

allow traffic to:

*.cloud.microsoft

Security Products

Review:

• Defender for Cloud Apps
• CASB solutions
• SWG solutions

for URL-specific policies.

⚙️ Impact on Nerdio Environments

Nerdio itself does not rely on SharePoint URLs for core functionality.

However organisations using:

• Scripted Actions
• Automation
• Custom onboarding workflows
• Reporting integrations

should review any scripts containing:

sharepoint.com

or

-my.sharepoint.com

hardcoded references.

🔍 Areas Administrators Should Audit

Custom Scripts

Search for:

sharepoint.com

Power Automate Flows

Review:

• HTTP connectors
• SharePoint integrations
• URL parsing logic

Third-Party Applications

Check:

• DLP tools
• CASB integrations
• Monitoring solutions

for SharePoint-specific URL dependencies.

Internal Documentation

Update:

• User guides
• Support documentation
• Knowledge articles
• Helpdesk procedures

🚨 Potential Risks

The biggest risk isn't Microsoft.

The biggest risk is:

👉 Custom code that assumes OneDrive will always use a SharePoint URL.

Common examples include:

• URL parsing scripts
• Custom web applications
• Browser extensions
• Security policies
• API wrappers

🧠 FABS Insight

For Azure Virtual Desktop and Windows 365 customers, this should be treated as:

A validation exercise rather than a migration project.

The vast majority of Microsoft services will continue working exactly as they do today.

The focus should be on identifying:

• Hardcoded URLs
• Security controls
• Network filtering dependencies

before users begin seeing the new domain.

✅ Recommended Actions

Immediate

• Inventory custom SharePoint URL usage
• Review firewall allow lists
• Review Conditional Access policies
• Review proxy configurations

Before Rollout

• Test OneDrive access in AVD
• Test OneDrive access in Windows 365
• Validate FSLogix ODFC behaviour
• Validate KFM (Known Folder Move)

During Rollout

• Monitor helpdesk tickets
• Monitor sign-in failures
• Monitor proxy and firewall logs

🏁 Final Thoughts

Microsoft's move to onedrive.cloud.microsoft is primarily a branding and simplification initiative.

For most Azure Virtual Desktop and Windows 365 users:

✅ No changes to workflows

✅ No changes to collaboration

✅ Existing links continue working

The organisations most likely to experience issues are those with:

• Custom integrations
• URL-dependent scripts
• Strict web filtering policies

Now is the perfect time to review those dependencies before the rollout begins.