Microsoft Roadmap, messagecenter and blogs updates from 16-11-2025

[Introduction]

We’re introducing a Data Security Investigations (DSI) lightweight cost estimator to help analysts model and forecast storage and compute unit costs based on specific use cases, enabling more accurate budget planning. In addition, a new usage report provides granular breakdowns of billed storage and compute unit usage, empowering DSI analysts to identify cost-saving opportunities and optimize resource allocation.

This message is associated with Microsoft 365 Roadmap ID 518225.

[When this will happen:]

• Public Preview: Rollout begins early December 2025 and completes by early December 2025.
• General Availability (Worldwide): Rollout begins early February 2026 and completes by late March 2026.

[How this will affect your organization:]

Who is affected: Admins and analysts using Data Security Investigations in Microsoft Purview.

What will happen:

• A new in-product cost estimator will be available to model storage and compute unit costs.
• A usage dashboard report will provide detailed billed storage and compute unit breakdowns.
• These features are designed to support pay-as-you-go billing transparency.
• The rollout will occur automatically; no configuration changes are required.
• Features will be enabled by default for all tenants.

Visual examples:

Screenshot 1: Data Security Investigations cost estimator

Screenshot 2: Data Security Investigations usage dashboard

[What you can do to prepare:]

• No admin action is required before rollout.
• Consider notifying your users about these changes.
• Update any internal documentation that references DSI billing or cost management.
• Learn more:
  • Billing in Data Security Investigations | Microsoft Learn
  • Learn about Data Security Investigations | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

To streamline workspace scheduling, users can now book a workspace directly from the location field when creating a calendar event. This enhancement simplifies the booking experience and aligns with user feedback requesting more intuitive workspace reservation options.

Screenshot: Open the location field to book a workspace through search or by selecting Browse workspaces

[When this will happen:]

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in early December 2025 and is expected to complete within the same timeframe.

[How this affects your organization:]

• Who is affected: All users in tenants where workspace booking is enabled by IT admins and users have turned on workspace booking in their settings.
• What will happen:
• Users will see a new option to search or Browse Workspaces directly from the location field when creating an event.
• On iOS, the existing long-press calendar compose button method for booking workspaces will be retired.
• This feature is ON by default but only applies if workspace booking is enabled by both the admin and the user.
• Admins must have already configured workspace bookings for this feature to be available in their organization.

[What you can do to prepare:]

• No admin action is required.
• If workspace booking is not yet enabled in your organization, consider reviewing the feature and enabling it to take advantage of this streamlined experience.
• Communicate the upcoming change to helpdesk staff, especially regarding the retirement of the iOS long-press method.
• Update internal documentation if it references the previous booking method.

Learn more: Configure rooms and workspaces for Room Finder in Outlook

[Compliance considerations:]

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

[Introduction]

Starting November 17, 2025, agents created in Agent Builder within Microsoft 365 Copilot will be able to generate Word, Excel, and PowerPoint content. This capability is part of the “Generate documents, charts, and code” skillset (formerly known as Code Interpreter), designed to help users complete common tasks more efficiently. These skills were first introduced in Microsoft 365 Copilot in October and are now extending to agents—bringing the same powerful creation tools into custom workflows.

This message is associated with Roadmap ID 506753.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-November 2025 and is expected to complete by early December 2025.

[How this will affect your organization:]

Who is affected:

• Microsoft 365 Copilot users with access to Copilot Studio.

What will happen:

• Users can generate Word, Excel, and PowerPoint documents by chatting with agents created in the embedded Copilot Studio experience.
• This capability is part of the “Generate documents, charts, and code” skillset (formerly known as Code Interpreter).
• No changes to existing admin policies.
• No admin action is required; this is for awareness only.

[What you can do to prepare:]

• Communicate this enhancement to helpdesk staff or internal champions.
• Remind users that this capability already exists in Copilot and is now extended to agent interactions in the embedded Copilot Studio experience.
• Learn more: Use Copilot Studio to build declarative agents

[Compliance considerations:]

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

[Introduction]

We’re introducing a new pay-as-you-go (PAYG) experience in the Microsoft 365 Admin Center (MAC). This update provides a centralized way to manage metered services such as Microsoft 365 Backup and Copilot under the Billing node.

[When this will happen:]

General Availability:

• Available to new Microsoft 365 Backup and all Copilot customers starting early December 2025.
• Migration path for existing Backup customers will be announced later.

[How this affects your organization:]

Who is affected: Admins in Worldwide and GCC environments managing Microsoft 365 Backup and Copilot PAYG services.

What will happen:

• A new PAYG page will appear under the Billing node in MAC.
• Admins can create and manage billing policies directly in MAC.
• Services can be linked to billing policies, with support for departmental billing. Note: departmental billing for Backup customers will become available in Q1 2026.
• Budgets can be set, and notifications triggered when thresholds are met.
• Usage and spending can be viewed at the billing policy level.
• Subscriptions and resource groups can be created in MAC without navigating to Azure.
• PAYG setup for other services remains under Org Settings > PAYG until transitioned.
• Additional PAYG-enabled services will be added to the Billing node over time. Until then, the PAYG setup for other products (besides Backup) will continue to remain under Org Settings > PAYG.

[What you can do to prepare:]

No action is required.

Admins may decide to:

• Review the new PAYG page under Billing in MAC.
• Monitor announcements for migration timelines for existing Backup customers.
• Refer to Microsoft documentation for guidance on billing policies and budget notifications.

Learn more: Microsoft 365 pay-as-you-go services documentation | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

To strengthen security and reduce the risk of ungoverned scripting, Microsoft is expanding the custom scripting governance in the App Catalog site. This change helps ensure a more secure and manageable environment in SharePoint Online.

What will happen:

Custom scripting will be disabled (setting DenyAddAndCustomizePages to 1 or $true) for the tenant-wide App Catalog site using the APPCATALOG#0 template.

When this will happen: Default custom scripting governance on the App Catalog site will take effect starting in mid-January 2026.

Who is affected: Admins managing the SharePoint tenant-wide App Catalog site and content inside.

How this affects your organization:

• App operations remain unaffected: Uploading, updating, and deploying SharePoint and Office apps will continue to work.
• Custom script-based changes will be blocked: New changes related to custom scripting in the App Catalog Site will be disabled by default; existing custom scripting related customizations will remain unaffected.

What you can do to prepare:

• Inform App Catalog site owners and helpdesk staff in your organization of this upcoming change to reduce confusion and support calls.

• To temporarily opt out of custom scripting governance for a specific site (effective for 24 hours with tenant admin approval), use the following PowerShell command:

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false

• To update the site property bag (by default disallowed when custom script governance is enabled), use the following PowerShell commands to enable it at tenant or site level:

Set-SPOTenant -AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled $true

Set-SPOSite <SiteURL> -AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled $true

Learn more: 

• Security considerations of allowing custom script | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
• Allow or prevent custom script | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
• Overview of the SharePoint Framework | SharePoint | Microsoft Learn

Compliance considerations:

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

[Introduction]

Coming soon to SharePoint: Tenant admins will be able to centrally manage site branding using PowerShell. This update supports consistent branding across all SharePoint sites by enabling enforcement of enterprise themes, disabling custom branding on specific sites, and auditing branding changes. These capabilities help organizations maintain a unified brand experience and improve governance.

This message is associated with Roadmap ID 526794.

[When this will happen:]

• Targeted Release (Worldwide): Begins late November 2025, completes mid-December 2025
• General Availability (Worldwide, GCC, GCC High, DoD): Begins mid-January 2026, completes late January 2026

[How this affects your organization:]

Who is affected: Tenant admins managing SharePoint Online branding and governance.

What will happen:

• Admins can disable or enable custom site branding per site using PowerShell.
• When site branding is disabled, site managers lose access to Site branding page in Site Settings.
• Admins can apply enterprise themes (including multi-color themes) to specific sites via PowerShell.
• Branding changes made via PowerShell are tracked for audit and accountability.
• New site creation scripts can include branding settings to ensure consistency from launch.
• Admins can remove existing Brand Center via PowerShell.
• Theme management via PowerShell is transitioning to a centralized model:
  • The primary geo will act as the central location for organization-wide theme creation and management.
  • Satellite geos will be able to view and apply themes from the primary geo using Get-SPOTheme and Set-SPOWebTheme cmdlets.
  • Themes previously created in satellite geos will remain available, but creating new themes in satellite geos will no longer be supported.

[Here’s what’s new:]

• Consistent branding enforcement: Admins can disable or enable custom branding per site. When disabled, site managers lose access to Site branding page in Site Settings.
• Automated theme application: Apply approved enterprise themes (including multi-color themes) to specific sites using PowerShell.
• Audit and transparency: All branding changes made via PowerShell are tracked, enabling visibility into who made updates.
• Automated site creation with branding: Embed theme settings directly into site creation scripts to ensure new sites launch with consistent branding.
• Easier Brand Center management: Admins can remove an existing Brand Center via PowerShell to reset or update branding controls.
• Centralized theme management across geos: Themes created in the primary geo are visible and applicable in satellite geos. Satellite geos can apply but not create new themes going forward.

[What you can do to prepare:]

• Review PowerShell documentation:
  • Set-SPOSite
  • Get-SPOTheme
  • Set-SPOWebTheme
• Upgrade your SharePoint Online Management Shell to the latest version after rollout.
• Communicate branding governance changes to your SharePoint admin team.
• Update internal documentation to reflect new PowerShell capabilities and theme management model.

[Compliance considerations:]

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

[Introduction]

To enhance wireless content sharing in meeting spaces, Microsoft Teams Rooms on Windows devices will soon support Miracast. This complements existing options like Teams Cast and HDMI ingest and is available for devices including touch boards. This feature is exclusive to Teams Rooms Pro.

This message is associated with Roadmap ID 506748.

• Targeted release: We will begin rolling out in mid-January 2026 and expect to complete by end of January 2026.
• General Availability: We will begin rolling out in end of January 2026 and expect to complete by mid-February 2026.

Who is affected: Admins managing Teams Rooms on Windows devices with Teams Rooms Pro licenses.

What will happen:

• Miracast will be available as a wireless sharing option in Teams Rooms on Windows.
• The feature will be OFF by default and can be enabled via a tenant-wide toggle in the IT admin portal.
• Laptop devices must support Miracast to use this feature.
• No impact to end-user workflow unless enabled by admin.

• Review your Teams Rooms device compatibility with Miracast.
• Enable the feature via the IT admin portal if desired.
• Communicate the availability of Miracast to helpdesk and meeting room support staff.
• Update internal documentation to reflect the new sharing option.

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