Microsoft Roadmap, messagecenter and blogs updates from 21-10-2025

Updated October 20, 2025: Removal of these pages have started in late October 2025 and will be fully completed by end of November 2025.

ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We encourage customers to move away from consuming these pages and use Microsoft Graph for remote operations where possible.

Please refer to the following information regarding the DISCO and WSDL endpoints

• These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
•  These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
• Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
• These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
• If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.

Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online – Microsoft 365 Developer Blog

Updated October 20, 2025: We have updated the timeline. Thank you for your patience.

When creating a presentation in Copilot for Microsoft PowerPoint, users will be able to reference a Microsoft Teams meeting.

A Microsoft 365 Copilot license is required to use this feature.

This message applies to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint on the web.

This message is associated with Microsoft 365 Roadmap ID 492979 (Windows desktop), Roadmap ID 492981 (Mac desktop), and Roadmap ID 492980 (web)

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-January 2026 (previously mid November) and expect to complete the rollout by late January 2026 (previously late November).

[How this will affect your organization:]

After this rollout, users will be able to reference Teams meetings when searching for files that Copilot can use to create a presentation. Select the Copilot icon from the PowerPoint ribbon and choose Create a presentation with file:

Search for a Teams meeting to reference it:

This feature will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more: Create a new presentation with Copilot in PowerPoint – Microsoft Support (will be updated before rollout)

Updated October 20, 2025: We have updated the rollout timelines and content below. Thank you for your patience.

In November 2025, we will expand the passkey (FIDO2) authentication methods policy in Microsoft Entra ID to support passkey profiles in public preview. This update will enable granular, group-based control over passkey configurations and introduce new API schema changes.

[When this will happen:]

Public Preview (Worldwide): We will begin rolling out early November 2025 and expect to complete by early December 2025.

Public Preview (GCC, GCC High, DoD): We will begin rolling out mid-November 2025 and expect to complete by mid-December 2025.

[How this will affect your organization:]

After this rollout, you’ll be able to apply different passkey configurations per user group. For example, you will be able to:

• Allow the use of specific FIDO2 security key models for user group A
• Allow the use of passkeys in Microsoft Authenticator for user group B

Important: If your organization opts-in to the new admin UX and modifies the Default passkey profile, the new schema will take effect. If you continue using Graph API or third-party tools to modify the policy, the schema will not change until General Availability.

These new settings will be available at Microsoft 365 admin center > Home > Security > Authentication methods > Passkey (FIDO2) settings:

As part of this update in November 2025, if Enforce attestation is disabled, we will start accepting security key or passkey providers using the following attestation statements:

• “none” 
• “tpm” 
• “packed” (AttCA type only) 
• Custom attestation formats ≤ 32 characters 

This will allow a wider range of security keys and passkey providers to be accepted for registration and authentication in Microsoft Entra ID. To compare this upcoming update with the current behavior, refer to Microsoft Entra ID attestation for FIDO2 security key vendors

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to review your current passkey configuration, notify your admins about this change, and update internal documentation.

Learn more about passkeys in Microsoft Entra ID: Enable passkeys for your organization – Microsoft Entra ID | Microsoft Learn (will be updated before rollout)

Updated October 20, 2025: We have updated the content to correctly reference Chromium 142. Thank you for your patience. 

[Introduction]

Upcoming privacy-related changes in Chromium-based browsers (Google Chrome and Microsoft Edge) will increase restrictions on local network access. When enforcement begins, users accessing OneDrive for Web (and some integrated Microsoft 365 experiences such as Microsoft Lists and SharePoint Document Libraries) will encounter a browser permission prompt for local network access unless the required policy is in place. If the permission is not allowed, performance optimizations and offline capabilities powered by OneDrive and Share Point will not be available. This communication provides required administrator actions to prevent loss of functionality.

[When this will happen:]

Chrome and Edge will roll out this privacy related change as part of Chromium 142 at the end of October 2025 (previously end of September).

[How this will affect your organization:]

If no action is taken:

1. Who is affected:
   • All users accessing OneDrive for Web, Microsoft Lists, and SharePoint Document Libraries via Chrome or Edge browsers.
   • Admins managing browser policies for Windows, macOS, and VDI environments.
2. What will happen:

   If no action is taken:

   • Users will see a new browser prompt requesting permission for local network access when opening OneDrive for Web and Lists.
   • If users do not click Allow, the following results occur on that device:
     • Performance acceleration will not be available (loss of faster data access behavior).
     • Offline functionality in OneDrive Web will not be available.
   • The experience will be slower and less resilient, and helpdesk contacts will increase due to unexpected prompts and missing offline capability.

   When the recommended browser policy is deployed in advance, the prompt is suppressed for the specified trusted Microsoft 365 endpoints and existing performance, and offline behavior are preserved. The policy prevents loss of existing capability and avoids user confusion.

   [What you need to do to prepare:]

   1. Identify Required Domains
      1. Include your organization’s SharePoint Online and OneDrive endpoints, for example: https://YOURTENANT-my.sharepoint.com or https://YOURTENANT.sharepoint.com
      2. Add additional sanctioned SharePoint Online host variations if applicable (e.g., specialized cloud environments). Avoid overly broad wildcards—conform to internal security governance.
   2. Configure Browser Policy
      1. Set the Chromium policy LocalNetworkAccessAllowedForUrls (Chrome Enterprise / Edge policy) to pre-authorize the listed domains.
      2. Apply via: ADMX / JSON for Windows; plist or configuration profile for macOS (Chrome and Edge).
      3. Roll out to all managed device groups (Windows, macOS, VDI as applicable).
      4. Even if the following policies are currently enabled by policy, deploy the allow-list to prevent future prompts and avoid user confusion.
         1. DisableNucleusSync
         2. DisableOfflineMode
   3. Remediation for Users Who Already Clicked Block
      1. Deploying the managed LocalNetworkAccessAllowedForUrls policy will override any prior per-user deny state and enforce the allow setting once the policy is applied to the device/profile; no end-user action is required after policy propagation.
      2. If you need immediate remediation before policy reaches the device, have the user open the affected OneDrive site, use the site (lock) icon, reset or change the local/network device access permission to Allow, then refresh.
   4. Ensure your Sync Client is updated to v.25.164

1. Per machine SKU: The Sync client will automatically apply the required permissions and policies for existing users in Chrome and Edge—no user action is needed.

2. Per user SKU: The Sync client will prompt users via a Windows Toast notification to enable these permissions. Users should follow the notification instructions to complete setup.

[Compliance considerations:]

Updated October 20, 2025: We have updated the rollout end date. Thank you for your patience.

[Introduction]

We’re introducing Viva Amplify in SharePoint, a new capability that enables communicators to distribute SharePoint news posts across multiple Microsoft 365 channels—including Outlook, Viva Engage, Teams, and additional SharePoint sites. This enhancement helps streamline content distribution and improve audience reach, all from within the SharePoint experience.

Screenshot: Amplify from SharePoint

This message is associated with Microsoft 365 Roadmap ID 473450.

• Targeted Release: Scheduled for early October

• General Availability: We will begin rolling out late September 2025 and expect to complete by end of October 2025 (previously mid October).

Who is affected: Users with a Viva Amplify license who create or manage SharePoint news posts.

What will happen:

• To Amplify a news post, first ensure the post is published. Once published, the Amplify button will appear in the SharePoint news post toolbar for users with edit access.
• Content is automatically optimized for each endpoint—no manual formatting required.
• Users with edit access to a published SharePoint news post can click the Amplify button in the toolbar to select channels and audiences, then publish the content across Outlook, Viva Engage, Teams, and other SharePoint sites.
• After a news post is amplified, communicators can select Analytics from the toolbar to view detailed engagement metrics. The Amplify Analytics help users understand how content is performing and where it’s having the most impact.
• Engagement metrics include (but are not limited to)
  • Total views
  • Unique views
  • Dwell time
  • Reactions
  • Engagement metrics by channel
• These insights help communicators analyze performance and tailor future content for better reach—all without leaving the SharePoint interface.

• No admin action is required unless you’ve created internal guidance for end users.
• Ensure relevant users have Viva Amplify licenses.
• Review and update any internal documentation or helpdesk materials that reference SharePoint news publishing.
• Communicate this change to content creators and corporate communicators.

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

Updated October 20, 2025: EDU tenants will have agent auto creation turned off by default on 10/20. If you wish to have agent auto creation turned on, you may do so in “Agent Settings” in the Teams Admin Center.

An agent for every channel: Teams channels provide an organized space for teams to manage workstreams and communicate with stakeholders. Now, each channel can have a dedicated agent that draws on its conversations and meetings to act as a domain expert for the team. These agents adopt the channel’s name and help with common tasks – for example, flagging important deadlines that are buried in conversations, summarizing progress with succinct status reports, assigning tasks and due dates, and answering questions asked in natural language like “What’s the latest on our budget?” You can even invite these agents into meetings when you need expert insights in the discussion.

• Status reporting: The agent can draft a status report for your project on your behalf. It pulls updates from channel conversations, meeting summaries, Planner boards, and announcements, organizing them into sections within the report. You can edit the draft directly in Teams before publishing it to the channel
• Providing answers: Instead of manually searching for information across posts and threads, simply ask the agent. It checks the channel’s conversations, meetings, and plans, and can also trigger a web search. Then it quickly compiles the insights, summarizes the information, and delivers a clear, actionable reply
• Planner integration: When a user assigns a task to another user via your channel’s agent, it creates a plan in Planner. Users can then ask the agent questions about the plan and the agent will keep them updated on the status of action items

Image 1 – Add an agent to a Teams channel:

Image 2 – Channel Agent participates in the conversation:

Limitations:

• Channel Agent may gather and share context that crosses information barriers.
• Channel Agent is best supported by English (US).
• Channel Agent is not supported in private channels.
• Channel Agent is not functional in channels that contain external or guest users.
• Channel Agent is not supported in tenants that use Customer Key.
• Processing data from previews can happen outside of the EU Data Boundaries

When this will happen:

• Public Preview: We will begin rolling out in mid-September 2025 and expect to complete by mid-October 2025.

How this affects your organization:

This new agent is available in public preview and customers are required to have the following licenses to access in public preview. Beyond preview access, additional licensing details will be communicated at general availability.

• An eligible Microsoft 365 base license.
  • For the list of eligible base licenses, see Understand licensing requirements for Microsoft 365 Copilot.
• Have an eligible Microsoft Teams license.
  • Teams licenses might be included in your Microsoft 365 subscription. If you have Microsoft 365 (no Teams) licenses, you need to purchase separate Teams licenses.
• Have a Microsoft 365 Copilot license.
  • For information on how to acquire Microsoft 365 Copilot licenses, see Where can I get Microsoft Copilot?.

Channel Agent and Microsoft 365 are built on Microsoft’s comprehensive approach to security, compliance, and privacy. Learn more about Microsoft Purview: Use Microsoft Purview to manage data security & compliance for Channel Agent in Teams.

For existing Teams channels, users will need to manually add an agent in to use its capabilities. To add an agent to a channel, open the side panel through the “Agents and Bots” button in the upper right-hand corner of the channel. Once the side panel is open, you will see a banner to add an agent to this channel.

An agent will be automatically added to newly created channels. This means that for any new channel that an eligible user creates, an agent will be automatically added to the channel. If you would like to change this behavior, IT admins can choose to update this in Teams admin center.

Within Teams admin center, in the Teams apps section you will see a new page called Agent settings, where you can manage the configuration for the auto-creation feature. By default, auto-creation is enabled. It can be disabled by turning the toggle off. 

What you can do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

The “Channel Agent” app will be turned on by default unless all apps are blocked by your organization. However, as an admin, you control whether Channel Agent will be available to your entire organization or to a certain group of users. For more information, refer to our admin documentation here.

To create Channel Agent, a user needs to be Copilot licensed, have the necessary admin permissions, and be an owner of the channel or have permissions to add/remove apps in the channel.

Documentation:

• Set up Channel Agent in Microsoft Teams
• Get started with Channel Agent in Microsoft Teams

Compliance considerations:

Updated October 20, 2025: We have updated the content below. Thank you for your patience. 

[Introduction]

To improve consistency across Microsoft 365 services and reduce reliance on Scope Search, Microsoft Teams will now respect hidden user attributes—such as ShowInAddressList and HiddenFromAddressListsEnabled—without requiring Scope Search. This change aligns Teams behavior with Outlook and Exchange, simplifying user visibility management and resolving issues caused by Scope Search, such as difficulty locating Call Queues and Auto Attendants.

Rollout begins early October 2025 and is expected to complete by late October 2025.

• Who is affected: Admins managing Microsoft Teams user visibility, especially those who previously used Scope Search to hide users.
• What will happen:
  • Teams will respect hidden user attributes (e.g., ShowInAddressList, HiddenFromAddressListsEnabled, msExchangeHiddenFromAddressList) without requiring Scope Search.
  • Guest users with ShowInAddressList set to False will no longer appear in People Search.
  • Scope Search is no longer needed to hide users.
  • If Scope Search is used for Information Barriers (IB), it should remain enabled.
  • This change aligns Teams behavior with Outlook and Exchange.

• Review your current use of Scope Search. If used solely to hide users, disable it.
• Ensure hidden user attributes are correctly configured:
  • Online: HiddenFromAddressListsEnabled
  • On-premises: msExchangeHiddenFromAddressList
  • Guest users: Set ShowInAddressList to True if they should appear in search results.
• Communicate this change to helpdesk and support teams.
• Update internal documentation to reflect the new behavior.
• For more details, refer to Microsoft Teams admin documentation.
• To verify your user configuration, run the Microsoft Teams Internal User Search Diagnostic.

[Compliance considerations:]

• Contextual Understanding: Copilot retains details from earlier prompts, such as file paths, parameters, or objects, for seamless reuse.
• Efficiency: Simplifies complex workflows by removing the need to retype information across multiple steps.
• Improved Accuracy: Ensures consistency and minimizes errors by accurately referencing previous inputs.
• Intuitive User Experience: Facilitates smoother, smarter automation creation with minimal effort.

[Introduction]

To improve the security and reliability of event email notifications in Microsoft Teams, we’re updating how custom HTML templates are supported. Starting November 17, 2025, organizations using premium custom HTML templates for Teams Events must ensure their sending domain is properly set up and authenticated. This change helps reduce the risk of event emails being flagged as spam or phishing by ensuring they originate from trusted, customer-owned domains.

This change will take effect on November 17, 2025.

• Who is affected:
  • Organizations using premium custom HTML templates for Teams Events email notifications.
• What will happen:
  • Users will no longer be able to edit or use custom HTML templates for Teams Events unless the sending domain is properly set up and verified.
  • Event emails must be sent from a domain authenticated within your tenant.
  • Microsoft will no longer send these notifications from its default external email address for these templates.

• Set up and verify your organization’s domain in Microsoft 365 tenant settings.
• Configure the domain to allow Microsoft products to send notifications from your organization’s email address.
• This is a one-time setup and must be completed before November 17, 2025.
• Refer to the official guidance for step-by-step instructions: Select domain to use for email from Microsoft 365 products

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

Support for Visio 2016 and 2019, Microsoft Project 2016 and 2019, and several other products also ended, October 14, 2025. Looking ahead, support for Office LTSC 2021 will end in one year—on October 13, 2026. Organizations using these products should upgrade as soon as possible to maintain security, compliance, and performance.

[How this affects your organization:]

After end of support, Office 2016 and Office 2019 suites, standalones, and servers will no longer receive security updates or other fixes, and no technical assistance will be available for devices still running them. Continuing to run unsupported software may expose your organization to security vulnerabilities and compliance risks and may affect the reliability and performance of services.

[What you can do to prepare:]

To mitigate these risks while maintaining access to desktop Office apps, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps (for enterprise or for business). Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy, and is eligible for use with the Microsoft 365 Copilot add-on.

For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported until October 2029 under the Fixed Lifecycle Policy.

Take steps to prepare for this transition with the following resources:

• Read the upgrade guidance for an overview of how to move from Office 2016 or Office 2019 to Microsoft 365 Apps.
• Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365.

Plan ahead to avoid potential disruptions and keep your organization’s software environment secure and up to date. 

We’re updating how we bill for mid-term subscription changes to improve clarity and efficiency.

[When this will happen:]

Starting November 13, 2025 changes to existing subscriptions—such as adding or removing licenses, cancellations, and upgrades—will be billed the next day instead of at the beginning of the following month. This change ensures more timely and transparent billing, helping you better track and manage your subscription costs.

When you see this change will depend on the country/region your account is in.

• Singapore and Italy: November 13, 2025
• Asia-Pacific: November 18, 2025
• Worldwide: January 6, 2026

[How this will affect your organization:]

If you have an account where your invoices start with a “G”, your organization will be impacted by this change on the date the change is launched in your region.

Example:

• If your account is in Singapore or Italy and you add a license to your subscription on November 13, you will receive an invoice for that additional license on November 14th.

Note: With this change is it possible to be billed later for changes made earlier in the month as changes made prior to this update will still be billed around the beginning of the following month.

[What you need to do to prepare:]

No action is required. This update will be applied automatically to all eligible subscriptions.