Microsoft Roadmap, messagecenter and blogs updates from 21-01-2026

Updated January 20, 2026: We have updated the timeline. Thank you for your patience.

Coming soon to Microsoft Teams: When users connect to their organization’s Wi-Fi, Teams can automatically set their work location to reflect the building they are working in. This makes it easier for users to coordinate work with their coworkers and connect in person.

This feature is opt-in and requires you to take action to configure it. After you turn it on, end-users remain in control and can choose whether to share their work location with their coworkers.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 488800.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early March 2026 (previously early February) and expect to complete by mid-March 2026 (previously mid-February).

[How this will affect your organization:]

This feature allows you to map Wi-Fi networks and devices to buildings, which allows your users to have their work location automatically updated when they connect. This is a major improvement over the current experience which relies on end-users to manually set their work location. When this feature is configured and enabled, Teams can automatically update the work location of users who connect their laptop to your organization’s Wi-Fi network or peripherals. The feature can leverage the mapping between your building names and your Wi-Fi networks to set the work location of your users to the right building. It can also leverage mappings to specific peripherals, such as monitors. Teams uses the same policy to enable or disable automatic updates of work location for Wi-Fi and peripherals. Learn more: New-CsTeamsWorkLocationDetectionPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Teams will not update the location of your users if they connect after their working hours (that they can configure in the Microsoft Outlook Calendar). Also, their work location will be cleared at the end of their working hours.

[What you need to do to prepare:]

Automatic update of work location is off by default, but it can greatly improve the experience of your users. We recommend turning it on and configuring it in your tenant.

Before rollout, we will update this post with new documentation.

Updated January 20, 2026: We have updated the timeline. Thank you for your patience. 

We’re introducing an enhanced organization chart experience in the Profile Card in Microsoft Teams for Windows Desktop, Mac, and Teams on the web. This update improves the user interface and navigation while maintaining the core browsing functionality. These changes are based on user feedback to streamline org chart exploration and reduce friction in navigating team structures.

This feature is associated with Microsoft 365 Roadmap ID: 500696.

Targeted Release: We will begin rolling out in early February 2026 (previously late January) and expect to complete in mid-February 2026 (previously mid-December 2025).

General Availability (Worldwide): We will begin rolling out in mid-February 2026 (previously mid-January) and expect to complete in late February 2026 (previously late January).

Who is affected: All users of Microsoft Teams on Windows Desktop, Mac, and web platforms.

What will happen:

• The organization chart in the Profile Card will receive UI/UX enhancements to improve navigation and usability.
• The focused individual remains centered when the manager chain is collapsed, improving visual clarity.
• Fewer clicks are needed to view another person’s Profile Card from the current view, reducing navigation effort.
• New navigation buttons allow users to scroll through previously viewed individuals within the same Profile Card instance, streamlining org chart exploration.
• The feature is enabled by default and requires no configuration changes.

Screenshot 1 – Updated Profile Card with centered individual and collapsed manager chain:

Screenshot 2 – Expanded organization chart view:

What you can do to prepare

• No admin action is required at this time.
• We recommend informing users about the improved navigation experience to help them take full advantage of the update.
• Update internal documentation or training materials if they reference the Profile Card experience.

Learn more (to be updated closer to rollout): Profile cards in Microsoft 365 | Microsoft Support 

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated January 20, 2026: We have updated the content. Thank you for your patience. 

Microsoft Graph now includes APIs that support Teams administration scenarios through beta:

• Teams User Configuration API – Available through V1.0
• Number Management APIs – Available through beta
• Policy Assignment APIs – Available through beta

These APIs enable programmatic access to user configurations, telephone number management, and policy assignments—helping organizations automate and scale Teams management. They are designed to support extensibility, automation, and integrations with your existing tools and workflows.

Please note that only Teams User Configuration API is currently available via the Microsoft Graph through V1.0, rest of the two APIs (Number Management and Policy Assignment) are currently available via the Microsoft Graph through beta. They are supported in commercial environments and accessible through both delegated and application permissions.

• Who is affected: Admins managing Teams users, policies, or voice configurations.
• What will happen:
  • Teams User Configuration API: Retrieve detailed Teams settings for users, including effective policy assignments and voice attributes. Details: List userConfigurations – Microsoft Graph v1.0 | Microsoft Learn
  • Number Management APIs: Retrieve telephone number details, assign, and unassign telephone numbers. Details: List numberAssignments
  • Policy Assignment APIs: Assign or unassign Teams policies for users. Details: teamsPolicyUserAssignment: assign

• Begin exploring the APIs using the Microsoft Graph V1.0/beta endpoints.
• Ensure your applications and scripts use the appropriate permission scopes.
• For feedback or questions, contact: [email protected]

Learn more:

• User Configuration Graph API – List userConfigurations | Microsoft Graph | Microsoft Learn
• Number Management Graph API(s) – List numberAssignments | Microsoft Graph | Microsoft Learn
• Policy Assignment/Un-Assignment Graph API(s) – teamsPolicyUserAssignment: assign | Microsoft Graph | Microsoft Learn

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated January 20, 2026: We are updating this post as a reminder. Thank you for your patience. 

[Introduction:]

As part of the Microsoft Secure Future Initiative (SFI) and in alignment with the “Secure by Default” principle, we’re retiring the legacy IDCRL (Identity Client Run Time Library) authentication protocol in SharePoint Online and OneDrive for Business. This change helps strengthen your organization’s security posture by enforcing modern authentication standards—OpenID Connect and OAuth—which reduce exposure to outdated and vulnerable authentication methods.

[When this will happen:]

• Starting January 31, 2026: Legacy client authentication will be blocked by default. Organizations may temporarily re-enable it using PowerShell until April 30, 2026.
• Starting May 1, 2026: Legacy client authentication will be permanently blocked and cannot be re-enabled.

[How this affects your organization:]

Who is affected:

• Organizations using clients, scripts, or applications that rely on the legacy IDCRL authentication protocol to access SharePoint Online or OneDrive for Business.

• Legacy authentication calls using IDCRL will be blocked by default starting January 31, 2026.
• Temporary re-enablement is possible via PowerShell until April 30, 2026.
• After May 1, 2026, IDCRL authentication will be permanently retired and cannot be re-enabled.
• Applications using IDCRL will fail to authenticate unless updated to use modern protocols.

[What you can do to prepare:]

We recommend migrating from legacy authentication protocols to modern authentication as soon as possible. 

To prepare for this retirement:

• Migrate all clients, scripts, and applications to use OpenID Connect or OAuth protocols. 
• Review current configurations for IDCRL authentication.
• Notify IT admins, app owners, and security teams about the upcoming retirement.
• Update internal documentation to reflect the new authentication defaults.
• Use telemetry to identify usage of legacy authentication protocols and monitor migration progress.
• Use PowerShell to manage legacy authentication settings if needed:
  • Set AllowLegacyAuthProtocolsEnabledSetting and LegacyAuthProtocolsEnabled to TRUE to temporarily allow legacy authentication until April 30, 2026.
• Learn more:
  • Migrating from IDCRL authentication to modern authentication in SharePoint | Microsoft 365 Developer Blog | Microsoft Dev Blogs
  • Set-SPOTenant (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

We’re expanding Data Loss Prevention (DLP) for Microsoft Fabric to include support for Fabric warehouses. DLP for Fabric is already generally available and helps organizations detect and protect sensitive data stored in structured data within OneLake. With this update, existing DLP policies can now extend protection to warehouse data, strengthening your organization’s overall data security and compliance posture.

[When this will happen]

General Availability (Worldwide): Rollout will begin in early February 2026 and is expected to complete by late February 2026.

[How this affects your organization]

Who is affected:

• Organizations using Microsoft Fabric with DLP policies scoped to Fabric and Power BI in Microsoft Purview, including organizations that use Fabric warehouses. Fabric warehouses are SQL-based analytical databases within Microsoft Fabric that store structured data for reporting, analytics, and business intelligence and are fully integrated with OneLake and other Fabric workloads.

What will happen:

• Existing DLP policies scoped to the Fabric and Power BI location will automatically begin scanning and evaluating Fabric warehouses in included workspaces.
• Admins who monitor DLP policies or billing will see warehouse objects included in the protected asset count in the Microsoft Purview pay-as-you-go invoice.
• No changes will be made to existing policy configurations.
• The feature will be enabled by default as it becomes available to your tenant.
• There is no impact on user workflows.

[What you can do to prepare]

No action is required. You may review existing policies or inform billing and compliance stakeholders of the updated protected asset coverage.

Learn more: Get started with data loss prevention policies for Fabric and Power BI | Microsoft Purview | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.