This guide walks you through tenant migration using Microsoft-supported steps first, with WPS only where it genuinely helps.
Problem Description: Need Remove Stale Federation
Please remove stale federation metadata and convert the domain `pop.solutionspt.com` from Federated to Managed. We receive a `FederationException` when running `Convert-MsolDomainToStandard`, even when executed directly on the ADFS server. ADFS is reachable, but the federation trust cannot be cleanly removed. if I try MgGraph, I get: PS C:\Windows\System32> Connect-MGGraph -Scopes "Domain.ReadWrite.All", "Directory.AccessAsUser.All" Welcome to Microsoft Graph! Connected via delegated access using 14d82eec-204b-4c2f-b7e8-296a70dab67e Readme: [https://aka.ms/graph/sdk/powershell]() SDK Docs: [https://aka.ms/graph/sdk/powershell/docs]() API Docs: [https://aka.ms/graph/docs]() NOTE: You can use the -NoWelcome parameter to suppress this message. PS C:\Windows\System32> Update-MgDomain -DomainId "pop.solutionspt.com" -AuthenticationType "Managed" Update-MgDomain_UpdateExpanded: Domain operation is not allowed. Status: 400 (BadRequest) ErrorCode: Request_BadRequest Date: 2026-01-20T14:45:54 Headers: Cache-Control : no-cache Vary : Accept-Encoding Strict-Transport-Security : max-age=31536000 request-id : fbd580e7-c39b-4fd7-ab9b-995a4e727f32 client-request-id : 96950744-b5d6-420a-865e-afebeb1a7f4c x-ms-ags-diagnostic : {"ServerInfo":{"DataCenter":"UK South","Slice":"E","Ring":"5","ScaleUnit":"000","RoleInstance":"LN2PEPF000114C5"}} x-ms-resource-unit : 1 Date : Tue, 20 Jan 2026 14:45:54 GMT Recommendation: See service error codes: [https://learn.microsoft.com/graph/errors]() I tried creating a ticket with the 365 team, and they said I need to create a ticket with the Entra Team and I've ended up here. Kind regards Pete
Quick Answer for Office Setup on New Device
To convert a federated domain to managed and address FederationException, first check that Active Directory Federation Services (AD FS) is running correctly; if so, specify the server using Set-MsolADFSContext -Computer
Likely Causes Behind Tenant Migration Root Factors
The Microsoft account or license context may not match the purchase or device.
Cached credentials, outdated builds, or damaged local components can trigger tenant migration.
A file-specific corruption or add-in conflict can mimic a broader application failure.
Recommended Solution: Restoring Office After Errors
When to use this: Apply these steps when the symptoms match and you can access the relevant Microsoft account or administrator.
If you cannot cleanly remove the federation trust, manually remove stale federation metadata through the AD FS Management console or PowerShell.
To bypass AD FS, use Set-MsolDomainAuthentication -DomainName "pop.solutionspt.com" -Authentication Managed to change the domain to managed.
Alternative Solutions for Secondary Migration Fixes
Retry the Microsoft-side steps after restarting the app and device.
Test the same action in a private browser session or a new blank file to isolate account vs file issues.
Capture exact error text and screenshots before contacting Microsoft Support or your administrator.
Working with WPS Office: WPS as a Local Alternative

WPS Office cannot replace Microsoft account, activation, or cloud fixes for this scenario. It remains one of the best free Microsoft Office-compatible alternatives for opening and editing local files.
Download and install WPS Office from the official website.
Open local Word, Excel, PowerPoint, or PDF files in the matching WPS app.
Save a working copy locally while Microsoft-side issues are resolved.
Return to Microsoft Office after the primary fix succeeds.
If you need a practical local workspace in the meantime, try WPS Office.
Prevention Tips for Keeping Office Stable Long Term
Keep one primary Microsoft account for subscriptions and Office sign-in.
Install updates for Office and Windows before retrying failed workflows.
Back up important files before repair, reset, or reinstall actions.
Document exact error messages before the next troubleshooting attempt.
FAQs About Office Support Questions
Can WPS Office fix this tenant migration issue directly? Only when the WPS steps match the formatting or file task. Account, activation, and cloud issues stay on the Microsoft side.
Should I reinstall Office before trying these steps? Not first. Confirm account, license, and the exact error before reinstalling.
What should I send to Microsoft Support? The affected account email, device type, Office version, exact error text, and screenshots with personal data hidden.




