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

Updated October 7, 2025: We have updated the timeline to show as intended as well as added additional details. Thank you for your patience.     

Introduction

To help organizations manage metered consumption costs for Microsoft 365 Copilot Chat, we’re introducing support for prepaid Capacity Packs in the Microsoft 365 admin center (MAC). This feature enables global administrators to use prepaid message bundles before incurring pay-as-you-go (PAYG) charges.

This update applies specifically to Copilot Chat environments provisioned via the Power Platform admin center (PPAC), including declarative or custom Copilot agents built using Microsoft Copilot Studio.

Each Capacity Pack includes 25,000 Copilot messages per month, which can be allocated to Copilot Chat environments via PPAC. Once enabled, MAC will prioritize usage from these prepaid packs and automatically switch to PAYG when capacity is exhausted.

Admins can monitor usage in PPAC, including:

• Total messages consumed
• Remaining prepaid capacity
• Message allocation per environment

This update is associated with Microsoft 365 Roadmap ID 496139.

• Targeted Release: We will begin rolling out in late September 2025 and expect to complete by late September 2025.
• General Availability (Worldwide): We will begin rolling out in late September 2025 and expect to complete by early October 2025.

This feature helps organizations manage Copilot Chat costs by allowing the use of prepaid message bundles before PAYG charges apply. It supports:

• Improved budget control through prepaid capacity
• Simplified billing setup in MAC
• Automated provisioning for Copilot Chat environments
• Enhanced cost visibility and governance through detailed usage reporting in PPAC

The feature also supports unlicensed users and includes automatic fallback to PAYG when prepaid capacity is exhausted, ensuring uninterrupted service.

Existing pay-as-you-go billing methods will remain available and unchanged. Capacity Packs offer an additional prepaid option and do not replace current billing models.

The feature is on by default and requires no manual configuration to begin using.

No admin action is required before rollout.

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

[Introduction]

[When this will happen:]

[How this affects your organization:]

Who is affected:

• Users will be able to back up their settings and Microsoft Store app installations on Windows 10.
• Users on Windows 11 will be able to restore these settings and apps during device setup.
• The feature is available once the cumulative update is installed but must be enabled by the admin.
• Admins can manage availability and configuration via policy settings.

What you can do to prepare:

• Ensure devices are updated with the September 2025 Windows Monthly Cumulative Update.
• Review and configure backup policies in your organization.
• Communicate this feature to helpdesk and support teams.
• Update internal documentation to reflect new backup and restore capabilities.
• Learn more: Windows Backup for Organizations 

Compliance considerations:

Microsoft Teams is introducing Search in Settings, a new capability that allows users to quickly locate specific settings using a search bar. This update improves discoverability and reduces friction by eliminating the need to manually browse through categories. The change is based on customer feedback requesting faster access to configuration options.

[When this will happen:]

Targeted Release: We will begin rolling out early November 2025 and expect to complete by early November 2025.

General Availability (Production, GCC, GCCHigh, DoD): We will begin rolling out early November 2025 and expect to complete by early November 2025.

[How this affects your organization:]

Who is affected: All users of Microsoft Teams across Microsoft 365 Tenants.

What will happen:

• A new search bar will appear at the top left of the Settings pane:



• Users can search by:
  • Category names (such as Notifications, Devices)
  • Section titles or subtitles within a category
  • Control titles or descriptions (such as Show message previews, Enable dark mode)
• The feature is enabled by default.
• No admin configuration is required.
• Existing settings remain unchanged.

[What you can do to prepare:]

No action is required at this time.

[Compliance considerations:]

• Does the change store new customer data?
• Yes. A new telemetry event is sent each time a user:
  • Finishes typing in the search box
  • Clicks the “x” to dismiss typed text
  • Clicks on a search result (includes setting ID and category)
  • Receives a “no results” message

All data is sent as UserBI telemetry and does not include personal content.

All other compliance considerations:

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

Introduction

We will retire the IP-based user location detection feature in the Microsoft 365 Suite Admin Portal bookmark creation flow, effective November 10, 2025. This change aligns with our ongoing investment in more secure and reliable location-based targeting using Azure Active Directory (Azure AD). Azure AD location-based targeting offers enhanced flexibility and better alignment with modern identity and access management practices.

When this will happen:

This change will take place on November 10, 2025. 

How this affects your organization:

• Who is affected: Admins using the Microsoft 365 Suite Admin Portal to create bookmarks with IP-based location targeting.
• What will happen:
  • Admins will no longer be able to target bookmarks based on IP-derived user location.
  • Azure AD location-based targeting will remain available and is the recommended alternative.
  • This change will be applied automatically; no configuration changes are required.

What you can do to prepare:

• No admin action is required for this change.
• Notify relevant users and helpdesk staff about the retirement of IP-based targeting.
• Update any internal documentation that references IP-based bookmark targeting.
• Review and familiarize yourself with Azure AD location-based targeting as the supported method going forward.

Compliance considerations:

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

1. Gets access to all the agent’s components with standard owner permissions, including delete permissions.
2. Gets the Environment Maker security role for the environment where the agent exists.

• Start or end a conversation.
• Start a conversation with an authentication token.
• Present options for persistent conversations and context variables.
• Send messages, including attachments and updates to context variables.
• Receive agent or system messages through webhook subscriptions.
• Check agent availability in a queue and retrieve both queue position and estimated wait time.

• Enhanced configuration experience: Enterprises can view the number of available and used IP addresses in a subnet. They can also troubleshoot configuration issues when the Virtual Network isn’t configured on a Power Platform environment.
• Extended connectors support for Virtual Networks: Support is now available for more connectors, including Azure AI Search and data export to Application Insights.

• Enable seamless integration with Contact Center Proactive Engagement.
• Manage the audience configuration and compliance profiles for your voice channel.
• Choose a Conversational Voice message in a journey by selecting a Contact Center Proactive Engagement.
• Design your journey to include conversational voice messages and react to message outcomes.
• View detailed engagement metrics, such as the number of attempts, outcomes, and specific results for each call interaction in the out-of-the-box journey reporting.
• Access all voice and engagement interaction data in storage and build custom reports using Microsoft Fabric integration.