Microsoft Roadmap, messagecenter en blogs updates van 04-12-2024

Updated December 2, 2024: We have updated the rollout timeline below. Thank you for your patience.

We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web). 

This message is associated with Microsoft 365 Roadmap ID 381953.

[When this will happen:]

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

General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 (previously mid-February) and expect to complete by late February 2025 (previously late March).

General Availability (GCC High, DoD): We will begin rolling out early April 2025 (previously early December) and expect to complete by late April 2025 (previously mid-January).

[How this will affect your organization:]

Longer URLs for meetings scheduled before the rollout will continue to work. The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

[What you need to do to prepare:]

You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL.

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

Updated November 27, 2024: We have the timeline below. Please note that customers who are interested in joining the preview must opt-in. To join the preview, customers should file a support ticket requesting to join the Scheduled prompts preview. Thank you for your feedback.

Coming soon for Microsoft Copilot for Microsoft 365: A new Scheduled prompts feature that allows users to automate Copilot prompts to run at set times and frequencies in Copilot in Microsoft Teams, Office.com/chat, and Microsoft Outlook for the web and Desktop. A Microsoft Copilot for Microsoft 365 license and a Standard Microsoft Power Automate license are required to use this feature. To be eligible, customers must also have the Optional Connected Experience (OCE) admin toggle enabled, and configure their DLP policies to allow the Copilot for Microsoft 365 connector in their default PowerPlatform environment.

This message is associated with Microsoft 365 Roadmap ID 401124.

[When this will happen:]

Public Preview: We will begin rolling out mid-December 2024 (previously mid-November) and expect to complete by late December 2024 (previously late November).

[How this will affect your organization:]

Before this rollout: Users are unable to schedule Copilot for Microsoft 365 prompts to run at a specific time and frequency.

After the rollout: Users can find the Scheduled prompts feature by hovering over a prompt they have submitted to Copilot or by clicking on the Schedule prompts button in the Copilot response footer (references images below). After configuring their Scheduled prompt, when a user selects the Save and activate button to confirm the scheduled prompt, a user’s prompt information will be sent to the Power Automate and Power Platform system, and the Power Automate terms of service and privacy policy apply:

Schedule prompt entry points

Schedule prompt Creation dialog

[What you need to do to prepare:]

Managing the Scheduled prompts feature as an admin: To continue having the Scheduled prompts feature available in your organization, no action is required after completing the opt-in process. The feature is automatically included as part of the Optional Connected Experiences admin setting, which is on by default.

Admins can access the Optional connected experiences setting at config.office.com

If you prefer not to have this feature available to your organization, you can file a customer support ticket requesting to exit the preview program or disable the optional connected experiences setting at config.office.com. For more information: Admin controls for optional connected experiences. If you turn off the Optional connected experiences setting, this action will prevent anyone in your organization from seeing the Scheduled prompts feature in Copilot. If you choose to make these optional connected experiences available to your users, your users will also have the option to turn them by going to the privacy settings dialog box. 

To prevent exposing organizational data, you should also create a data policy in the Power Platform admin center. Creating a data policy in the center allows administrators to control access to these connectors in various ways to help reduce risk in your organization. Learn more here: Data policies – Power Platform | Microsoft Learn

If you disable this feature after someone in your organization has already used the feature:

• Users will no longer be able to manage previously scheduled prompts.
• Sessions for previously run scheduled prompts will continue to exist.
• Users will no longer see the Scheduled prompts feature or the prompt management pane.

Relevant articles

• Data, Privacy, and Security for Microsoft Copilot for Microsoft 365 | Microsoft Learn
• Security in Microsoft Power Platform – Power Platform | Microsoft Learn
• Admin controls for optional connected experiences in Overview of optional connected experiences in Office – Deploy Office | Microsoft Learn

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

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle 

Updated December 2, 2024: We have updated the content. Thank you for your patience.

We’re making it easier for users to access the Microsoft Places app. This app is accessible on the web, or as an app inside Teams, Outlook and the Microsoft 365 app.

The Microsoft Places app helps users coordinate their in-office days with colleagues. When work location is shared from OWA or the new Outlook Calendar, users will see others’ work locations and can decide the best days to be in the office for in-person collaboration.

Users with Teams Premium will have access to additional features in the Microsoft Places app:

• Team Guidance for leaders to communicate which days their team should plan to be in the office and what the priorities are for each in-office day. Providing a purpose for team days in the office gives you another reason to come into the office. Team Guidance will be ON for all Teams Premium users. Admins can selectively turn off this feature following these instructions.
• Places Explorer to discover what’s happening in the office, who’s in the office, and find places like services and amenities. Admins will need to configure buildings and floors for Places Explorer to show building details.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early December 2024 and complete by mid-December 2024.

[How this will affect your organization:]

With this change, the Places app will be accessible by default for all users by navigating to this URL, but you need to take action to make it easier to discover inside Teams,  Outlook and the Microsoft 365 app. To improve the user experience, admins can set up policies to pin the Places app for your users.

[What you need to do to prepare:]

If you were part of the Microsoft Places Preview and followed the onboarding instruction, access to the Places app is likely restricted to users in the ‘PlacesUsers’ Security Group. You need to take action to broaden access to other users in your tenant, as described here. 

If you were not part of the Preview and want to restrict access to the Places app, you can do so today by using PowerShell: Set-PlacesSettings – EnablePlacesWebApp Parameter. Access restriction will apply to the app on the web and inside Teams, Outlook and Microsoft 365 app.

Additional References

If you want to keep the Places app OFF for the entire tenant, you can do so using PowerShell:

#Connect to Microsoft Places:

Connect-MicrosoftPlaces

# Update the settings for access to buildings in the location settings:

Set-PlacesSettings -EnableBuildings Default:false

# Update the settings for access on the controllable core experience:

Set-PlacesSettings -EnablePlacesWebApp Default:false

Updated December 3, 2024: We’re delaying further rollouts of warning banners and blocking pages in December and intend to resume in mid-January. We’ll have a more detailed update later.

In today’s security climate, our work across the company and greater industry to keep this critical ecosystem secure is more important than ever. And while we also ship bug fixes and other new features via continuous innovation, in the end security is job one.

Keeping Microsoft Teams up to date is critical to ensure your devices are secure and compliant. By default, and as designed, Teams updates automatically which successfully updates most clients in the world without additional overhead for customers.

Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the Teams desktop client be kept up to date. This is not a new policy, for instance in MC298823 (November 2021), a version that is far out of date will become incompatible with the service until it’s updated. As documented, when a client falls out of date, the user will see:

• Recurring in-app alerts, if the app is between 30d-90d out of date.
• A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web.

As an example, if the Teams app is hypothetically on a version released on January 1 and the next update is fully available on January 15, an in-app alert would be shown on February 14th (30 days after the January 15th update).

For reference, link to the Teams app’s version’s release dates. Also, The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization.

Classic Teams is not in scope for this post; see MC783985 for Classic Teams Timelines regarding end of support and end of availability.

[When this will happen:]

The existing policy enforcement will be visible beginning November 12th, 2024.

[How this will affect your organization:]

New Teams – Windows & Mac Versions desktop clients (not running in a VDI environment)

• Beginning November 12th, 2024, Teams desktop clients >30d out of date, will present a banner or notification to users that they are on an outdated version of Teams. For reference,
  • Windows client versions less than 24231.512.3106.6573 are impacted on November 12.
  • Mac client versions less than 242507.3125.3475 are impacted on Nov 12.
• (On hold) Beginning December 4th, 2024, Teams desktop clients older than 90d out of date, will present a blocking page. They will be shown an option to update to the latest version of Teams from this page or use Teams on the web. For reference,
  • Windows client versions less than 24193.1805.3040.8975 are impacted on December 4th.
  • Mac client versions less than 24215.1002.3039.5089 are impacted on December 4th.

New Teams app running in a VDI environment – Windows desktop clients will follow the same policies as non-VDI environments, with enforcement starting on dates below

• Beginning January 13th, 2025, for clients more than 30d out of date will get a banner or notification to users that they are on an outdated version of Teams.
• Beginning February 3rd, 2025, for clients older than 90d out of date, the Teams desktop client will present a blocking page.

Note: The enforcement policies on preview rings may start mid-November. The 30d out of date in app messaging and 90d out of date blocking dates still apply (for versions released to that ring)

[What you can do to prepare:]

To avoid disruption to end-users, the admins with users on Teams versions older than the currently released versions, should update their users to the most recent version.

Admins should make sure Teams is automatically updating to stay current and within the compatibility window. Common configurations to validate include:

• Teams clients on macOS have Microsoft AutoUpdate (MAU) configured properly. Learn More
• Customer network settings, and any device management software e.g. antivirus, are configured properly to allow automatic updates.
• Windows Policies must not block new Teams or the Webview2 updater.

Please visit this page to learn more.

Updated December 2, 2024: We have updated the rollout timeline below. Thank you for your patience.

If your organization does not have frontline workers, you can ignore this message.

Coming soon for the Shifts app in Microsoft Teams, we will expand the functionality of the time clock export report by adding additional fields from Shifts. This enhancement provides you with a more comprehensive and detailed view of your scheduling data, making it easier to analyze and manage workforce activities. This message applies to Teams for web, Windows, and Mac desktops.

This message is associated with Microsoft 365 Roadmap ID 422812.

[When this will happen:]

General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 (previously early December) and expect to complete by late January 2025 (previously mid-December).

[How this will affect your organization:]

To take advantage of the expanded functionality of the time clock export report, familiarize yourself with the new fields added from Shifts. Review your current reporting processes and update any relevant documentation or training materials to incorporate these changes.

This change will be on by default.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required before the rollout. You may want to notify your users about this change.

Updated December 3, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to new Microsoft Outlook for Windows desktop and Outlook for the web: Notifications will be batched in the Notifications pane.

Batches are groups of cards in the user’s Notification pane separated by subject. Items from the same email thread, document, spreadsheet, etc. will be grouped into a batch. This message applies to new Outlook for Windows and Outlook for the web.

This message is associated with Microsoft 365 Roadmap ID 470021.

[When this will happen:]

Targeted Release: We will begin rolling out early December 2024 (previously late November) and expect to complete by late December 2024.

General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by early February 2025.

[How this will affect your organization:]

Users can access the Notification pane by selecting the bell icon in the top right corner of Outlook. Batched notifications have a chevron (^) in the top right corner. Users can expand the chevron to see all related messages:

This feature will be available by default.

[What you need to do to prepare:]

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

#newoutlookforwindows

Updated December 3, 2024: We have updated the content. After further review, we are not able to proceed with these clouds: GCC High and DoD. We apologize for any inconvenience.

Coming soon to Microsoft Outlook: Users can move emails between their accounts in the new Outlook for Windows, streamlining organization and productivity. For enterprise users, this feature is controlled by the Set-OWAMailboxPolicy policy managed by admins in Microsoft Exchange PowerShell. By enabling this policy, admins can grant their users the ability to move emails between accounts in a way that aligns with organizational needs and policies. With this rollout, we are introducing a new parameter called -ItemsToOtherAccountsEnabled for the Set-OWAMailboxPolicy policy.

This message is associated with Microsoft 365 Roadmap ID 470018.

[When this will happen:]

Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by late February 2025.

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

General Availability (GCC): We will begin rolling out early March 2025 and expect to complete by mid-March 2025.

General Availability (GCC High, DoD):  We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

The new parameter -ItemsToOtherAccountsEnabled controls whether users can move or copy their emails between accounts. By default, the value will be False, which means that the policy is disabled and users won’t be able to move emails between accounts unless an admin changes the policy to True.

If you enable this parameter, users will be able to move emails between accounts in these ways:

1. Dragging and dropping an email from one account to another

2. Using shortcuts:

• Copy: Ctrl C + Ctrl V
• Copy: Ctrl + Drag and drop
• Move: Drag and drop
• Move: Ctrl X + Ctrl V

3. Right-click an email and select Move or Copy from the menu (menu items only available if the policy is enabled)

[What you need to 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.

Learn more: Set-OwaMailboxPolicy (ExchangePowerShell) | Microsoft Learn

#newoutlookforwindows

Viva Pulse will retire the Customize the privacy policy statement feature in the Privacy settings. Instead, Viva Pulse will reference the Microsoft admin center’s Organizational privacy policy, which is an existing capability for Microsoft apps. This retirement eliminates duplicate capabilities.

[When this will happen:]

This retirement will take place on January 6, 2025.

[How this will affect your organization:]

Current experience to be retired: Viva Pulse > Privacy > Customize Privacy policy statement:

After the retirement: Configure your organization’s privacy policy in the Microsoft admin center > Org settings > Security & privacy tab > Privacy profile > Organization privacy statement:

[How this will affect your organization:]

• Your organization’s privacy policy used in Viva Pulse and displayed to survey participants will be derived from the policy you configure in the Microsoft admin center, rather than from the Viva Pulse Privacy settings.

[What you need to do to prepare:]

Ensure that your organization’s privacy policy is configured in the Microsoft admin center. If it is not configured, the default privacy policy that will be used in Viva Pulse and displayed to survey participants will be the Microsoft Privacy Statement – Microsoft privacy.

Learn more

• Set up the in-app Viva Pulse experience | Microsoft Learn

Coming soon for Microsoft Outlook for iOS and Android users: In response to customer requests, we are rolling out the ability to attach emails directly in the compose window. This enhancement allows users to include individual emails as attachments in new messages, facilitating seamless sharing and providing more context for recipients.

This message is associated with Microsoft 365 Roadmap ID 464206.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High): We will begin rolling out early January 2025 and expect to complete by late February 2025.

[How this will affect your organization:]

Before this rollout, users can forward emails as attachments but cannot attach emails while composing.

After this rollout, users will notice a new Attach email option when they select the paper clip attachment icon in the compose window. Users can select this option to browse for, choose, and attach individual emails to their new message.

This change is available by default.

[What you need to do to prepare:]

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation.

8 new Copilot feature metrics are now generally available in the Copilot Dashboard and Viva Insights Advanced insights. The new Copilot feature metrics being added, include:

• “Intelligent Recap” actions taken in Teams
• “Visualize as table” actions taken in Word
• “Chat (Copilot in Word)” prompts submitted in the in-app chat section in Word
• “Add content to presentation” actions taken using PowerPoint
• “Organize presentation” actions taken using PowerPoint
• “Chat (Copilot in PowerPoint)” prompts submitted in the in-app chat section in PowerPoint
• “Chat (Copilot in Excel)” prompts submitted in the in-app chat section in Excel
• “Business Chat (web)” prompts submitted. This feature is also known as “Copilot with Enterprise Data Protection” and the insights include prompts submitted through Edge and the Microsoft 365 app.

As part of this update the “Total actions taken” numbers will also be updated to reflect activity related to the Copilot features listed above. “Total number of active Copilot users” and “Percentage of active Copilot users” already included the features above, but will be impacted by the addition of Business Chat (web).

Starting in early Devember, 2024, anyone with access to the Copilot dashboard will be able to view these insights. Anyone with the Viva Insights analyst role will be able to query the usage information related to these features through Viva Insights Advanced Insights. Note that in Copilot dashboard, these metrics and insights only show up for measured employees with a Microsoft 365 Copilot license. Measured employees also need to be assigned a Viva Insights license for their data to be available in Viva Insights Advanced insights.

This message is associated with Microsoft 365 Roadmap ID 418379 and Roadmap ID 467249.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in early December 2024 and expect to complete by mid-December 2024.

[How this will affect your organization:]

As a result of adding these new Copilot feature metrics, users can expect to see a significant increase in the “Total number of active Copilot users” (Copilot dashboard – “Adoption” tab) as well as the “Total actions taken” (Copilot dashboard – “Impact” tab). 

[What you need to do to prepare:]

Share this information with anyone who has access to the Copilot dashboard and or Viva Insights Advanced Insights. Make sure that anyone who needs access gets the appropriate role assigned. For more information, visit:

• Roles in Viva Insights | Microsoft Learn for access to Viva Insights Advanced Insights
• Manage settings for the Microsoft Copilot Dashboard | Microsoft Learn for access to Copilot dashboard

Coming soon, Microsoft Purview Insider Risk Management will be rolling out risky AI usage detections

This message is associated with Microsoft 365 Roadmap ID 394281

[When this will happen:]

Public Preview: We will begin rolling out early December 2024 and expect to complete by mid-December 2024.

General Availability (Worldwide): We will begin rolling out mid-February 2025 and expect to complete by late February 2025

[How this will affect your organization:]

With this update, Insider risk management will help admins identify risky AI usage. We are adding new detections of intentional and unintentional insider risk activity on generative AI apps that can pose a risk to an organization. Activities will include risky prompts containing sensitive info or risky intent and sensitive responses containing sensitive info or generated from sensitive files or sites. Coverage will span across M365 Copilot, Copilot Studio and ChatGPT Enterprise. These detections will also contribute to Adaptive Protection insider risk levels.

[What you need to do to prepare:]

Below are some of the steps admin can take

1. Get insights into risky AI usage at an organization level in an anonymized form using analytics
2. Create Risky AI usage policy to track risky prompts and sensitive responses in M365 Copilot, Copilot Studio
3. The activity explorer in alerts gives a single threaded view of prompt, response along with the sensitive information present
4. Use the new Generative AI indicators in adaptive protection for user risk score

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. 

Main Admin link: Learn about insider risk management policy templates | Microsoft Learn

Coming soon for Microsoft Teams: Users will be able to reduce the main Teams window, the chat window, and the meeting stage to 360px wide or 502px wide, compared to the current minimum supported dimensions of 720px wide, with no loss of functionality. We will bring this change to the rest of Teams when we release in General Availability.

Also, users can adjust the width of Teams side panels as desired.

This update enhances accessibility, creates new multitasking opportunities, supports efficient window management on Windows 11 and macOS desktops, and offers greater zooming capabilities for low-vision users when scrolling in one dimension.

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

This message is associated with Microsoft 365 Roadmap ID 470431.

[When this will happen:]

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

We will communicate the plan for General Availability in a future post.

[How this will affect your organization:]

Your organization will be able to resize down to smaller window sizes and to resize left and right panes.

Resizing windows:

Reflowing windows:

This change will be available by default.

[What you need to do to prepare:]

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

The same Messages search vertical at microsoft365.com will soon be available for organization-wide search in Microsoft SharePoint. Search verticals are tabs on the search result page that show results of a specific type or from select sources. For example, the Files vertical shows results classified as files and makes it easy for users who are looking to find documents.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early January 2025 and expect to complete by mid-January 2025.

[How this will affect your organization:]

This feature will be on by default.

If you have disabled the Messages search vertical for microsoft365.com, the Messages search vertical will also be disabled in SharePoint. Learn more: Manage search verticals | Microsoft Learn

Before this rollout: Default vertical experience without the Messages vertical:

After this rollout: New default vertical experience with the Messages vertical:

[What you need to 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.

We are excited to announce new features in the Copilot Prompt Gallery (formerly Copilot Lab), designed to enhance AI value and engagement within your organization:

[When this will happen:]

Available now

[How this affects your organization:]

As announced at Ignite:

• Copilot Lab is now Copilot Prompt Gallery: The product name has been updated to drive clarity of the product’s purpose and functionality and to align with the enhancements we are making to the product based on customer feedback.
• Save and share a prompt with a co-worker: Users can now create and save a prompt in Microsoft 365 Copilot Business Chat. And later this year, they will be able to share that prompt via a copy link or email from Copilot Prompt Gallery. Learn more about how users can save a prompt here and how users can share a prompt here. 
• Agent prompts: Copilot Prompt Gallery now supports prompts for agents, allowing users to discover and use agent prompts provided by their organization that are tailored to specific roles, functions, and tasks. And later this year, users will be able to save and share these prompts to inspire others on the team.

Coming soon:

• New Copilot Prompt Gallery app in Microsoft 365: Explore full prompt collections across Copilot and agents in the new Prompts app available on Teams, Outlook, and www.microsoft365.com.
  

Learn more about the Copilot Prompt Gallery Ignite announcements here: New Copilot Prompt Gallery helps you discover, save, and share your favorite prompts 

Coming soon for Microsoft Teams: Users will no longer need to manually install and update the Network Device Interface (NDI). After this rollout, users will be able to turn on automatic installation and updates in Teams Settings. This improvement applies exclusively to Teams for Windows desktops.

This message is associated with Microsoft 365 Roadmap ID 429537.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out mid-January 2025 and expect to complete by late January 2024.

[How this will affect your organization:]

Users can enable the new feature in Teams > Settings > App permissions > Production tools.

This user-facing change will be available to users with no admin controls.

[What you need to do to prepare:]

The improvement will be rolled out to organizations automatically with no admin action required. It is recommended that you notify your event organizers about this change and update any documentation as appropriate.

User documentation: Broadcasting audio and video from Microsoft Teams with NDI and SDI technology – Microsoft Support (will be updated before rollout)

Starting in late-December, Microsoft Copilot and Microsoft 365 Copilot users signed in with an Entra account will be able to upload images in both Work and Web copilot and ask Copilot questions about the image, such as for Copilot to analyze or describe it. Users will be able to take pictures using their mobile cameras or upload images directly to Copilot from their devices. This functionality will be available when using Microsoft 365 Copilot and Microsoft Copilot from following locations:

• Microsoft 365 app (Web, desktop, mobile)
• Outlook app (Web, desktop, mobile) 
• Teams (Web, desktop, mobile) 

 [When this will happen:]

General Availability: We will begin rolling out late December 2024 and expect to complete by mid-January 2024.

[How this will affect your organization:]

With these enhancements, Microsoft 365 Copilot will now understand non-animated images and will have support for major image types. Copilot will do its best to interpret the image, but the quality and content of the image can affect responses.

This feature will roll out to all endpoints and users will be able to use it without any tenant level configuration support. Any controls in place to limit the availability of Copilot for users will be honored.

1. Open the Intune Portal. 
2. Navigate to Devices > All devices. 
3. Select a device from the list. 
4. In the device Properties, navigate to Hardware. 
5. Locate the Security section to find TPM information, including the version and status. 

1. Open the Configuration Manager console. 
2. Navigate to Assets and Compliance > Overview > Device Collections. 
3. Select the desired device collection.  
4. Select a device and select Start > Resource Explorer. 
5. In the Resource Explorer, expand Hardware > Security > TPM. 
6. Check the version information and status from the TPM resource. 

• Find more information and advice in TPM 2.0 – a necessity for a secure and future-proof Windows 11.
• Prepare for Windows 10 end of support by moving to Windows 11 today.
• Learn more about Trusted Platform Module technology.
• Review which Windows features require TPM support.
• Read Windows 11 minimum system requirements and the PC Health Check app.

• Use service admin roles to manage your tenant
• Microsoft Entra built-in roles