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

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

Introducing a new content picker for Teams Mobile Android. Attach any type of content, whether files or media, from the paperclip icon in the compose overflow menu. Our unified attach flow makes it easy and intuitive to attach content from any source location.

This message is associated with Microsoft 365 Roadmap ID 488091.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out on Android early June 2025 and expect to complete by late June 2025.

General Availability (GCC, GCC High, DoD) We will begin rollout on Android late June 2025 and expect to complete by end of February 2026 (previously late September 2025)

[How this will affect your organization:]

Users will see an improved content attach flow in the Teams Android app.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated January 14, 2026: We have updated the timeline. This feature will now be included as part of another update referenced in MC796790. Administrators will gain the ability to manage Microsoft 365 certified SaaS applications through org-wide settings for third-party apps. No changes will be applied to tenant-wide settings unless initiated by an administrator. Thank you for your patience.

This feature will empower administrators to manage the availability of trusted Microsoft Teams apps based on rules, for enhanced security. Admins will be able to manage Microsoft 365 certified apps in the Teams admin center through a new control in Org-wide settings. You can further customize the availability of these apps based on permissions accessed and publisher names. The system automatically checks the Microsoft 365 certified apps that meet all the conditions you specify and makes those apps available.  

This message is associated with Microsoft 365 Roadmap ID 485712.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, you cannot manage at bulk the availability of Microsoft 365 certified apps. They are only controlled by third-party app tenant settings.

After this rollout, you can manage Microsoft 365 certified apps availability from org-wide settings in the Teams admin center at Manage apps > Actions > Org-wide app settings > Microsoft 365 certified apps. 

You can configure additional criteria from the Customize availability option:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before or after 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. This new control will be disabled by default.

Learn more: Manage org-wide app settings in Manage your apps in the Microsoft Teams admin center – Microsoft Teams | Microsoft Learn (will be updated before rollout)

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

[Introduction]

To improve mobile productivity and streamline file access, Outlook for Android will soon support in-app PDF attachment previews. This update aligns with user feedback requesting faster, more integrated document viewing experiences without needing to switch apps.

This message is associated with Roadmap ID 520386.

[When this will happen:]

General Availability (Worldwide): Rollout begins in late November 2025 and is expected to complete by end of January 2026 (previously late December).

[How this affects your organization:]

Who is affected:

• All users of Outlook for Android across commercial and education tenants.

What will happen:

• Users will be able to preview PDF attachments directly within the Outlook for Android app.
• The built-in previewer will launch automatically when a PDF is opened.
• Users can still choose to open PDFs in other apps via the overflow menu.
• This feature will be enabled by default; no admin configuration is required.

[What you can do to prepare:]

No action is required. This feature will be enabled automatically.

Optional steps:

• Communicate this change to helpdesk staff to reduce potential support inquiries.
• Update internal documentation if you reference mobile attachment handling.
• If your organization prefers users to use a specific PDF viewer, consider communicating usage guidance.

[Compliance considerations:]

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

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

[Introduction]

To support frontline workers using personal devices, Microsoft is introducing a dynamic onboarding wizard for Microsoft Teams. This experience is designed to simplify setup on Android and iOS devices, especially in environments with security policies like multi-factor authentication (MFA) and mobile application management. The wizard adapts automatically to your organization’s policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption.

This message is associated with Roadmap ID 523213.

[When this will happen:]

• Public Preview: Rollout begins in late November 2025 and is and expected to complete by mid-January 2026
• General Availability: Rollout begins in mid-March 2026 (previously mid-February) and is and expected to complete by end of March 2026 (previously end of February)

[How this affects your organization:]

• Who is affected: Frontline workers setting up Microsoft Teams on personal Android or iOS devices
• What will happen:
  • A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs
  • The wizard dynamically adjusts based on your organization’s security policies
  • Supports MFA setup, with emphasis on Microsoft Authenticator push notifications
  • This tool is optional and designed to improve BYOD Microsoft Teams adoption

[What you can do to prepare:]

• Review the admin documentation to understand the onboarding wizard’s capabilities and limitations
• Consider integrating the wizard into your new user onboarding workflows
• Communicate availability to helpdesk and frontline managers
• Update internal documentation if you support BYOD Microsoft Teams deployment
• Review documentation at the following link: Set up frontline Teams on personal devices

[Compliance considerations:]

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

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

Introduction

We’re enhancing the macOS file management experience by integrating Microsoft 365 Copilot directly into Finder. This update allows users to interact with Copilot to ask questions about their OneDrive files, streamlining productivity and making file insights more accessible.

Note: This update applies to OneDrive on macOS. Copilot integration in Finder requires a Microsoft 365 Personal or Family subscription, or a work or school account with a Microsoft 365 Copilot license. The rollout is gradual, so availability and functionality may vary by user and region.

When this will happen

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-November 2025 and is expected to complete by mid-February 2026 (previously late December 2025).

How this affects your organization

• Who is affected: All users of OneDrive on macOS with Copilot licensing.
• What will happen:
  • Users can right-click a OneDrive file in Finder, open the “OneDrive context menu”, and select Ask Copilot to query file contents:

   

  • This feature is enabled by default.
  • No admin configuration is required.
  • Available in all Microsoft 365 environments.

What you can do to prepare

• Inform users about the new Copilot capabilities in Finder.
• No admin action is required to enable the feature.
• Review Copilot licensing and availability: Which Copilot is right for me or my organization? | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

Learn more: Get started with Copilot in OneDrive | Microsoft Support

Compliance considerations

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

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

[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 February 2026 (previously mid-January) and is expected to complete by mid-February 2026 (previously mid-January).

[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.

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

[Introduction]

We’re enhancing SharePoint site analytics to include usage data from OneNote files (.one). This update provides a more complete view of site engagement by incorporating OneNote activity into metrics such as Unique viewers and site visits. Popular content reporting will also reflect heavily used OneNote files.

This message is associated with Roadmap ID 537285.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-February 2026 (previously mid-January) and is expected to complete by mid-March 2026 (previously mid-February).

[How this affects your organization:]

• Who is affected: Admins and users who monitor SharePoint site analytics.
• What will happen:
  • Expect an increase in reported site usage metrics, including unique viewers and site visits, as OneNote file activity will now be included.

  

  • The Popular content section in site analytics will display OneNote files if they are among the most accessed in the last 7 days.

  

  • No admin configuration changes are required; this update is enabled by default.

[What you can do to prepare:]

• Inform site admins and analytics stakeholders that site usage metrics may increase due to inclusion of OneNote activity.
• Update any internal documentation or reporting processes that reference SharePoint site analytics.
• No additional action or configuration is required.

Learn more: View usage data for your SharePoint site

[Compliance considerations:]

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

• January 2026 security update: Phase 1 of hardening begins. Hands-free deployment continues to be supported and can be explicitly disabled to enhance security. Use the new Event Log alerts and registry key options.
• April 2026 security update: Phase 2 of hardening follows. Hands-free deployment will be disabled by default but can be re-enabled, if necessary, with an understanding of the associated security risks.

• Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WdsServer\Providers\WdsImgSrv\Unattend
• DWORD name: AllowHandsFreeFunctionality
• Value data: 00000000

• Read the full hardening guidance: Windows Deployment Services (WDS) Hands-Free Deployment Hardening Guidance related to CVE-2026-0386.
• Learn more about the related vulnerability: CVE-2026-0386.
• See deployment alternatives: Windows Deployment Services (WDS) boot.wim support.
• Explore cloud-based solutions: Windows Autopilot and Windows Autopilot device preparation documentation.

[Introduction]

We’re improving channel meetings in Microsoft Teams by reducing automatic meeting updates in channel conversations. This change helps keep channels cleaner and focused on real user replies, while meeting details remain accessible when you open the meeting thread.

[When this will happen:]

• Targeted Release: Rolling out mid-January 2026, expected to complete by late January 2026.
• General Availability (Worldwide): Rolling out early February 2026, expected to complete by late February 2026.
• General Availability (GCC, GCCHigh, DoD): Rolling out early March 2026, expected to complete by late March 2026.

[How this affects your organization:]

• Who is affected: All Microsoft Teams users participating in channel meetings.
• What will happen:
  • Automatic meeting updates in channel conversations will be reduced.
  • Channel threads will appear cleaner and reply counts will reflect actual user responses.
  • Meeting details remain accessible by opening the meeting thread.
  • No admin configuration changes are required; the feature is enabled by default.

[What you can do to prepare:]

• No action is required. This update will roll out automatically.
• Optional: Communicate this change to helpdesk staff to reduce potential confusion.
• For more information on channel meetings, visit: Channel meetings in Teams.

[Compliance considerations:]

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

[Introduction]

We’re enhancing Microsoft Purview Content Explorer with new summary metrics to improve visibility into scanning and classification activities. These updates will help admins identify unscanned files and monitor classification trends, enabling better data governance and informed decisions.

This message is associated with Roadmap ID 526796.

[When this will happen:]

• Public Preview: We will begin rolling out late January 2026 and expect to complete by mid-February 2026. 
• General Availability (Worldwide): We will begin rolling out early March 2026 and expect to complete by late March 2026. 

[How this affects your organization:]

• Who is affected: Admins managing Microsoft Purview Information Protection and using Content Explorer.
• What will happen:
  • A new Unscanned Files Summary will display the count and percentage of files not scanned for classification.
  • Classification History Insights will show trends and details of classification changes over time.
  • These metrics will appear in Content Explorer alongside existing Sensitive Information Types (SITs) and labels.
  • Admins can explore the new metrics to identify gaps and use on-demand classification capabilities to retrigger scans if needed.
  • No changes to existing policies or configurations; the feature is enabled by default.

    

[What you can do to prepare:]

• No action is required.
• These metrics will automatically appear in Content Explorer.

[Compliance considerations:]

[Introduction]

Microsoft is expanding Edge for Business policy management in the Edge management service. In addition to existing Windows policy configurations, organizations will be able to configure Edge for Business policies for macOS, iOS, and Android devices in one place. This enhancement will streamline cross‑platform policy management and support more consistent browser governance across devices. 

This message is associated with Microsoft 365 Roadmap ID 522536.

[When this will happen]

• Public Preview (Worldwide): We began rolling out in mid-November 2025 and expect to complete by late January 2026.
• General Availability (Worldwide): We will begin rolling out in late January 2026 and expect to complete by early February 2026.

[How this affects your organization]

Who is affected:

• Admins who manage Microsoft Edge for Business using the Edge management service
• Organizations deploying Edge on Windows, macOS, iOS, or Android

What will happen:

• You will be able to configure Edge for Business policies for macOS, iOS, and Android directly in the Edge management service.
• Existing Windows configuration policies remain unchanged.
• You can edit an existing Windows configuration policy or create new policies that target multiple platforms: 



• Some policy settings will continue to apply only to Windows devices.
• No user impact unless your organization deploys new or updated policies.

[What you can do to prepare]

No action is required before rollout. After the feature becomes available:

• Review existing configuration policies and update them if you want to apply settings to macOS, iOS, or Android.
• Update internal admin documentation if you manage Edge policies across platforms.
• Learn more about configuration policies in the Edge management service.

Learn more: Get started with configuration policies | Microsoft Edge | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We are adding new, more granular permissions for users to get access to administrative areas in Viva Glint. These areas include Advanced Configuration, Nudges, General Settings, and Viva Integrations. We are also updating the name of the highest privileged role in Viva Glint to “Viva Glint Service Admin,” and for increased security, restricting the ability to assign new Viva Glint Service Admins to the Microsoft Admin Center (MAC) only.

[When this will happen:]

General Availability (Worldwide): Rollout will begin early February 2026 and complete by early February 2026.

[How this affects your organization:]

Who is affected: Admins managing Viva Glint roles and permissions.

What will happen:

• Additional permissions will be introduced for Advanced Configuration, General Settings, Nudges, and Viva Integrations.
• Assigning Viva Glint Service Admins will only be possible through the MAC.
• M365 Global Admins and Viva Glint Tenant Admins will have sole responsibility for assigning Service Admins.
• All Viva Glint Service Admins will have Advanced Configuration access going forwards
• No changes to existing admin policies; this update enhances security and role clarity.

[What you can do to prepare:]

• Review your organization’s needs to determine how to use these new permissions
• Ensure that only M365 Global Admins or Viva Glint Tenant Admins are prepared to assign Service Admins via MAC.
• Update internal documentation and communicate these changes to your helpdesk or support teams.

Learn more about Viva Glint roles and permissions: Viva Glint documentation.

[Compliance considerations:]

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

[Introduction]

We’re adding a new setting in Microsoft Teams for Desktop and Web that lets users select what happens when they press Enter while composing a message. This update responds to customer feedback for more control and helps prevent accidental message sends. It also aligns Teams with behavior in other messaging apps, creating a familiar and predictable compose experience.

This message is associated with Microsoft 365 Roadmap ID 537279.

[When this will happen:]

• Targeted Release: Rollout will begin in early February 2026 and complete by mid-February 2026.
• General Availability (Worldwide, GCC): Rollout will begin in mid-February 2026 and complete by late February 2026.
• General Availability (GCCH, DoD): Rollout will begin in early March 2026 and complete by mid-March 2026.

[How this affects your organization:]

Who is affected: All users of Microsoft Teams for Desktop and Web.

What will happen:

• A new setting will appear under Settings > Chats and channels: “When writing a message, press Enter to…”



• Users can select:
  • Send the message (default for all users)
  • Start a new line (to send, press Ctrl + Enter or Cmd + Enter)
• Teams will show contextual hints near the compose box to remind users of the current behavior.



• Additional behavior:
  • Shift + Enter will always insert a new line.
  • Teams will show contextual hints near the compose box to remind users of the current behavior.
• Applies only to Desktop and Web.
• This setting is per-user and will roam across devices.
• There is no admin control, policy, or Graph API configuration.

[What you can do to prepare:]

No admin action is required.

• Notify your helpdesk that users will see a new setting affecting how messages are sent.
• Update any internal documentation that references Teams compose behavior.
• Share this explanation with users: “Teams now lets you select whether Enter sends your message or creates a new line. The default is ‘Press Enter to send.’ You can change this in Settings > Chats and channels.”

There are no changes to Data Loss Prevention (DLP), compliance boundaries, or message retention.

[Compliance considerations:]

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

[Introduction]

Microsoft 365 Copilot in PowerPoint will soon support enterprise image libraries hosted on Adobe Experience Manager (AEM). This integration allows users to generate slides using branded images from your organization’s asset library, helping maintain brand consistency and streamline content creation.

This message is associated with Roadmap ID 516037, 516038, and 516039.

[When this will happen:]

General Availability (Worldwide): Rollout begins early February 2026 and is expected to complete by end of March 2026

[How this affects your organization:]

Who is affected:

• Organizations using Adobe Experience Manager for brand asset management
• Admins and brand managers configuring enterprise image libraries
• PowerPoint users leveraging Microsoft 365 Copilot

What will happen:

• Admins can connect enterprise image libraries from AEM to Microsoft 365 Copilot in PowerPoint.
• Users will be able to generate slides using branded images from AEM.
• If no enterprise image library is connected, the branded image option will be disabled, and only Microsoft 365 images will be available.
• This feature is available by default for admins to configure; no opt-in required.

[What you can do to prepare:]

• Deploy AEM assets Microsoft 365 Copilot Connector by following the steps outlined in the article Deploy the Adobe Experience Manager Assets Microsoft 365 Copilot connector.
• Give your final consent on the Adobe Experience Manager Assets screen



• Ensure images in AEM include robust metadata (keywords, titles, alt-text) for better searchability.
• Communicate this change to your design and marketing teams.
• Update internal documentation if you detail image sourcing for PowerPoint.

Once setup is complete, users can select the New Slide with Copilot icon in the PowerPoint ribbon, enter a prompt, and choose their preferred image source—either Microsoft 365 images or their organization’s branded image library—via the Image Source menu.

Learn more:

• About Adobe Experience Manager Assets Microsoft 365 Copilot connector
• Keep your presentation on-brand with Copilot

[Compliance considerations:]

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

[Introduction]

We’re retiring the ability to create alert policies and generate DLP alerts for sensitive data activities on endpoints in the Microsoft Defender portal. This change unifies endpoint data loss prevention (DLP) detection and alerting under Microsoft Purview DLP, giving organizations a more consistent experience and access to advanced enforcement and investigation capabilities in Microsoft Defender XDR.

[When this will happen]

• February 16, 2026: Sensitive data activity options will be removed from new alert policy creation in the Microsoft Defender portal.
• March 23, 2026: Existing alert policies using these activities will stop generating alerts.

[How this affects your organization]

Who is affected:

• Organizations that use alert policies in Microsoft Defender XDR to monitor sensitive data activities on endpoints.
• Admins who create or manage alert policies in the Microsoft Defender portal.

What will happen:

• The following endpoint-sensitive data activities will be retired and removed from alerting in the Microsoft Defender portal:
• Copying sensitive data to removable media, remote shares, or the clipboard
• Uploading sensitive files to third-party apps or services
• Accessing sensitive files with unallowed apps
• New alert policies cannot use these activities after February 16, 2026.
• Existing alert policies will stop generating alerts after March 23, 2026.
• These activities will not be re-enabled in the Defender portal after retirement.
• Organizations can continue to detect and alert on these activities using Microsoft Purview DLP, which supports:
• Alerting and incident creation
• User notifications through policy tips
• Activity blocking and restriction
• Unified investigation of DLP and security alerts in Microsoft Defender XDR
• Purview DLP alerts for these endpoint activities appear in the Defender XDR experience for triage and investigation.

[What you can do to prepare]

• Review existing Microsoft Defender alert policies to identify any that use the retiring activities.
• Re-create required alerting using Microsoft Purview DLP policies.
• Notify security operations and helpdesk teams about the retirement and the shift to Purview DLP.
• Update internal documentation that references these Defender alert policies.
• Review endpoint DLP configuration and policy guidance: Get started with endpoint data loss prevention | Microsoft Purview | Microsoft Learn.
• If none of your Defender alert policies rely on these activities, no action is required.

[Compliance considerations]

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

[Introduction]

Microsoft Defender for Cloud Apps is updating the Microsoft 365 connector configuration page with revised default values for new connector setups. These improvements are designed to help security administrators more easily understand the Microsoft Entra data signals required to support SaaS Identity–related security features. This update also reduces the likelihood of misconfigurations so that capabilities such as SaaS Identity Discovery, Threat Protection, Response, and Posture insights continue to receive the data they depend on.

This is also a good opportunity to verify that your existing connector configurations are set correctly for the security features in your environment.

[When this will happen]

We will begin rolling out in mid-January 2026 and expect to complete by late January 2026.

[How this will affect your organization]

Who is affected: Admins who manage Microsoft Defender for Cloud Apps and configure the Microsoft 365 connector.

What will happen:

• Existing connectors will not be modified. All current connector settings will remain unchanged for privacy reasons.
• The configuration page in the Microsoft 365 connector will receive an updated layout to clarify required permissions.
• New default values will apply only to newly created Microsoft 365 connectors.
• Limiting access to required Microsoft Entra signals may reduce threat detection coverage and posture accuracy.

[What you need to do to prepare]

• Review your current configuration of Microsoft 365 connector settings to ensure required Entra permissions remain enabled:

 

• To do this:
  1. Go to Microsoft Security platform > Settings > Cloud apps > App connectors.
  2. Select Microsoft 365.
  3. Choose Edit settings.
  4. Ensure that all required checkboxes are selected (All except “Microsoft 365 files”).
  5. Select Connect Microsoft 365.
• Inform your security and identity teams about the updated UI so they are prepared once the refreshed layout becomes available.
• Update internal documentation as needed.

Learn more: Connect Microsoft 365 to Microsoft Defender for Cloud Apps – How Defender for Cloud Apps helps protect your Microsoft 365 environment | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We are ending support for the SQL Server Reporting Services (SSRS) Report Viewer SharePoint Webpart feature. This change aligns with our efforts to simplify integration and improve reliability by using modern embedding methods. Instead of the Webpart, we recommend embedding SSRS reports in SharePoint using URL parameters.

[When this will happen:]

Support for the SSRS Report Viewer SharePoint Webpart will end on April 13, 2026.

[How this affects your organization:]

• Who is affected: Organizations using the SSRS Report Viewer Webpart in SharePoint.
• What will happen:
  • The SSRS Report Viewer Webpart will no longer receive updates or support after April 13, 2026.
  • Users can still download and use the component, but it will not be maintained.
  • No changes will occur automatically in existing SharePoint environments; the feature will remain functional but unsupported.

No admin action is required for this change. However, we recommend transitioning to the alternative approach: embed SSRS reports in SharePoint using URL parameters: 

Learn more:

• SSRS URL Access Parameter Reference
• SSRS SharePoint Webpart documentation.

[Compliance considerations:]

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

We've released updates to the following update channels for Microsoft 365 Apps:

• Current Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel

[When this will happen:]

We'll be gradually rolling out these updates of Microsoft 365 Apps to users on those update channels starting January 13th, 2026 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download these latest updates and begin deployment.

[What you need to do to prepare:]

To get more details about these updates view the following release notes:

• Current Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel

• Create and manage ticket types for your event and its sessions. Set pricing, limits, and access rules.
• Customize your registration form to include ticket selection as part of a seamless signup flow.
• Integrate with a trusted payment provider of your choice for secure checkout experiences. Reduce friction and abandoned registrations.
• Automatically send attendees a QR code-enabled event pass, making entry and session check-ins effortless.
• Eliminate manual reconciliation with real-time payment tracking.

• The opportunity to sign up for private preview is open now and until February 13, 2026. 
• First sign-in restore will become generally available in early 2026. 

• Those users who miss the OOBE restore option 
• Microsoft Entra hybrid joined, multi-user setups, and Windows 365 Cloud PCs 

• Read the blog article: Windows Backup for Organizations expands to first sign-in restore. 
• Sign up for the private preview: https://forms.office.com/r/UbE2AeP1yP.