Updated July 17, 2025: We have updated the timeline. Thank you for your patience.
To enhance security and reduce potential data exposure, we are updating the behavior of the Get-FederationInformation
cmdlet in Exchange Online. This change limits the scope of domain data returned by the cmdlet.
[When this will happen:]
General Availability (Worldwide, GCC, GCC-High, DoD): Rollout will begin in late June 2025 (previously mid-June) and is expected to complete by late August 2025 (previously early July).
[How this affects your organization:]
Previously, the Get-FederationInformation
cmdlet returned all federated domain information in the DomainNames field. After this update, the cmdlet will only return domain information that is explicitly passed as a parameter. This change may impact scripts or tools that rely on retrieving all federated domains by default.
There is no change to the cmdlet’s availability or core functionality—only the scope of data returned is affected.
[What you can do to prepare:]
- Review any automation, scripts, or tools that use the
Get-FederationInformation
cmdlet to ensure they explicitly pass the required domain(s) as parameters. - Communicate this change to your Exchange Online administrators and support teams to avoid confusion or unexpected results.
- For more details, refer to the official blog post: Important Update to the Get-FederationInformation Cmdlet in Exchange Online
Source: Microsoft
<<< [MC1081538] Archive
Tooltip: View earlier revisions of this post
Latest Posts
- AWS Lambda enables developers to debug functions running in the cloud from VS Code IDE
- AWS Lambda announces low latency processing for Kafka events
- AWS Lambda bridges console to VS Code for unified serverless development experience
- Amazon DynamoDB Streams introduces a new API feature for faster and more efficient stream shard discovery