| (Updated) Microsoft Purview: Role management updateCategory:Microsoft PurviewNummer:MC1199765Status:stayInformed | Updated April 16, 2026: We have updated the timeline and content. Thank you for your patience. [Introduction]
To strengthen security when Microsoft Purview interacts with Microsoft 365 services (Exchange, SharePoint, OneDrive, and Teams), we’re updating how roles are managed in Microsoft Purview. Certain admin roles in Purview will now be mapped to three newly created roles in Microsoft Entra. Role assignments will be synchronized between Purview roles and Entra roles without any customer action. This ensures that user permissions and identity flow securely from Purview to Microsoft 365. M365 services will only allow high-privileged operations like search/export to Purview users with the correct level of permissions in Entra, further protecting customer data.
[When this will happen:]
- General Availability (Worldwide): Rollout begins mid-February 2026, finishes by late May 2026 (previously late March).
[How this affects your organization:]
Who is affected: All customers with admins assigned to high-privileged roles in Purview that access Microsoft 365 data. These admins will have their assignments synced to Entra, meaning they will be assigned membership to mapped Entra roles.
What will happen:
- New roles will be created in Entra to map to Purview roles listed below.
- Existing role assignments will sync automatically.
- New assignments will sync from Purview to Entra within 15 minutes.
- If an admin has multiple Purview roles, they will receive the highest privilege Entra role: Administrator > Writer > Reader.
- Customers may see new Purview-specific Entra roles in audit logs.
- Do not assign to these roles directly in Entra; Purview manages them.
Role Mapping Table:
| Purview Role(s) | Mapped Entra Role |
|---|
Insider Risk Management Analysis
Insider Risk Management Investigation
Compliance Search
Export
Privacy Management Admin
Privacy Management Analysis
Privacy Management Investigation
Privacy Management Permanent Contribution
Privacy Management Temporary Contribution
Privacy Management Viewer
Data Security Investigation Reviewer | Purview Workload Content Reader |
Hold
Privacy Management Investigation
Data Security Investigation Investigator | Purview Workload Content Writer |
Search and Purge
Data Security Investigation Admin
Data Security Investigation Analyst (New Role) | Purview Workload Content Administrator |
Example: If you have both Export and Search and Purge roles, you’ll get the Purview Workload Content Administrator role in Entra.
Audit logs: The Audit logs will look like below, with Display Name always shown as “PurviewRoleAssignmentMigrator”. 
New Value for Role would always be one of the 3 new Entra roles created in Entra for protecting Purview customers 
[What you can do to prepare:] - No action is required.
- You will see these changes in assignments in the Entra Audit logs. These changes will happen in two modes:
- Bulk/One time update when all existing assignments to Purview roles are synced with Entra. This will be done once for each customer. This will generate extra activities in the Entra Audit logs as all previous assignments are synced from Purview to Entra.
- Continuous mode: all changes made subsequently in assignments for these Purview roles will be kept in sync with Entra. Customers will see these changes in Entra Audit Logs too. The amount of activity in audit logs will be in sync with the changes being made to Purview roles by admins.
- Active Assignments in Privileged Identity Management (PIM)
- Although the 3 new Entra roles are PIM-enabled, the assignments made to them by the sync process will be active (not eligible). If customers have PIM-enabled security groups assigned to Purview roles, then the same PIM-enabled security groups will be assigned to these 3 new Entra roles.
- Do not manually assign these roles in Entra; Purview will overwrite changes.
- For more details, review Microsoft Purview documentation.
[Compliance considerations:]
No compliance considerations identified; review as appropriate for your organization. |
| (Updated) Microsoft Defender for Office 365: Enhancing how we handle promotional mailCategory:Microsoft Defender XDRNummer:MC1279093Status:planForChange | Updated April 16, 2026: We have updated the timeline and content. Thank you for your patience. [Introduction] We are enhancing how Microsoft Defender for Office 365 identifies and manages promotional email. Promotional messages will be tagged as “promotions” (previously “Bulk” in preview) and can be moved automatically to a new Promotions folder. The system learns from user actions, such as moving messages into or out of the Promotions folder and applies those preferences to future messages. These improvements reduce inbox clutter and help users stay focused while still receiving promotional content they want. [When this will happen] - Public Preview (Limited): We will begin rolling out in mid-April 2026 and expect to complete by end of April 2026 (previously late April). To be included in the public preview program, send an email to [email protected] indicating: Organization name, Tenant ID and your onmicrosoft.com domain (e.g contoso.onmicrosoft.com) . Slots are limited and will close on April 30th, 2026.
- General Availability (Worldwide): We will begin rolling out in early July 2026 and expect to complete by late July 2026.
- General Availability (DoD, GCC, GCC High): We will begin rolling out in early July 2026 and expect to complete by mid-August 2026.
[How this affects your organization] Who is affected - All organizations that use Microsoft Defender for Office 365 across Worldwide, GCC, GCC High, and DoD clouds
What will happen - Incoming promotional messages will be tagged as “promotions.” (previously “Bulk” in private and public preview)
- If the Bulk Moves Enabled setting is turned on, tagged messages will automatically move to a Promotions folder created in user mailboxes.
- The system will learn from user actions when they move messages into or out of the Promotions folder. Future messages will follow the learned behavior.
- Users will be able to create inbox rules that reference the promotions tag.
- During the Public Preview:
- Tagging will be opt-in and configured using Exchange transport rules.
- Folder routing will be enabled through anti-spam policy settings (“Bulk moves enabled”).
- Both features will be able to be scoped to pilot security groups for a staged rollout.
- At Worldwide General Availability, tagging will be enabled by default for all tenants and will always remain that way.
Figure one – Admin configuration for tagging using exchange transport rule (required for public preview opt-In):  Figure two – Admin configuration for Bulk moves enabled to provision the promotions folder:  Figure three – System tagging of “Promotions” in outlook client and promotions folder (previously tagged as “Bulk” in private and public preview):  Figure four – User inbox rules using the promotions” tag:  [What you can do to prepare] - To be included in the public preview program, send an email to [email protected] indicating: Organization name, Tenant ID and your onmicrosoft.com domain (e.g contoso.onmicrosoft.com). Slots are limited and will close on April 30th, 2026.
- Review your internal mailbox and message handling guidance and update training materials if needed.
- If you plan to participate in the Public Preview, review your Exchange transport rule and anti-spam policy configurations to determine if you want to opt-in.
- Monitor the product documentation. A link will be added to this post when it becomes available.
[Compliance considerations] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed? | Yes. Incoming email will receive the promotions classification and may be moved automatically to the Promotions folder depending on admin configuration. | Does the change introduce or significantly modify AI or ML that interacts with customer data? | Yes. The system learns from user actions when they move messages and applies that learning to future similar messages. | | Does the change include an admin control, and can it be controlled through Entra ID group membership? | Yes. Admins can enable or disable Bulk Moves Enabled and can opt in to tagging during Public Preview. These controls can be scoped using existing admin delegation models. | | Does the change allow a user to enable or disable the feature themselves? | Yes. Users can override tagging behavior by moving messages in or out of the Promotions folder, which trains the ML model and adjusts future message handling. |
|
| General Availability: Microsoft Entra passkeys on WindowsCategory:Microsoft EntraNummer:MC1282568Status:stayInformed | [Introduction]
Microsoft Entra passkeys on Windows will soon be Generally Available, enabling phishing‑resistant, passwordless sign‑in to Microsoft Entra‑protected resources from Windows devices. The Public Preview of this capability was previously announced in MC1247893. Users can create device‑bound passkeys stored in the Windows Hello container and authenticate using Windows Hello methods (face, fingerprint, or PIN). This expands passwordless authentication support to Windows devices that aren’t Microsoft Entra‑joined or registered, helping organizations strengthen security and reduce reliance on passwords across corporate‑managed, personal, and shared device scenarios.
[When this will happen:]
- General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete by mid‑June 2026.
- General Availability (GCC, GCC High, DoD): We will begin rolling out in early July 2026 and expect to complete by late July 2026.
How this affects your organization:
Who is affected:
Organizations using Microsoft Entra ID with passkeys enabled in the Authentication Methods policy whose users sign in from Windows devices, including: - Corporate‑managed PCs
- Personal devices
- Shared devices
What will happen: With this General Availability release:
- Microsoft Entra passkeys on Windows will no longer require explicit opt‑in through Windows Hello AAGUID allow‑listing in a passkey (FIDO2) profile.
- This represents a change from Public Preview behavior, where administrators were required to explicitly allow Windows Hello AAGUIDs in a passkey profile for Microsoft Entra passkeys on Windows to function.
- If your passkey profile allows device‑bound, non‑attested passkeys:
- Users scoped to that profile will now be able to register and use Microsoft Entra passkeys on Windows by default without additional administrator configuration.
- As a result:
- Users in scope of passkey profiles that allow device‑bound, non‑attested passkeys may begin registering and using passkeys on Windows devices.
- If Conditional Access policies allow:
- Passkeys can be created and used on Windows devices that are not Microsoft Entra‑joined or registered, including personal or shared PCs.
- Each Windows device requires separate passkey registration per Entra account.
- Windows Hello for Business remains recommended for managed, Microsoft Entra‑joined or registered devices.
- Passkeys on Windows supplement unmanaged or shared device scenarios and do not support device sign‑in.
- Attestation is not currently supported for Microsoft Entra passkeys on Windows but is planned for a future update.
What you can do to prepare:
No action is required for most organizations. If you do not want users to register or use Microsoft Entra passkeys on Windows:
- Update the relevant passkey (FIDO2) profile to block Windows Hello AAGUIDs.
- Review existing passkey profiles that allow device‑bound, non‑attested passkeys.
- Add Windows Hello AAGUIDs to the block list in passkey profiles where passkey usage on Windows devices should not be permitted.
Learn more: Enable Microsoft Entra passkey on Windows | Microsoft Learn (will be updated before GA rollout) [Compliance considerations:] | Compliance area | Explanation | | Does the change modify, interrupt, or disable Conditional Access policies? | Existing Conditional Access policies continue to govern whether passkeys can be created or used on unmanaged Windows devices. | | Does the change include an admin control and can it be controlled through Entra ID group membership? | Admins can control passkey availability through Authentication Methods policies and FIDO2 passkey profiles scoped to Microsoft Entra ID groups. | | Does the change allow a user to enable and disable the feature themselves? | Users may register Microsoft Entra passkeys on Windows devices if permitted by administrator policy configuration. |
|
| Agent Builder in Microsoft 365 Copilot: Updates to the agent creation experienceCategory:Microsoft Copilot (Microsoft 365)
Microsoft 365 Copilot ChatNummer:MC1282682Status:stayInformed | [Introduction]
We’re updating the user experience in Agent Builder to make agent creation clearer, faster, and more intuitive. Based on customer feedback, these changes improve visual clarity and help users better understand how describing an agent, configuring it, and testing it work together—without changing how agents function or how they’re managed.
This update focuses only on the agent creation experience. There are no changes to agent capabilities, publishing behavior, or admin controls.
[When this will happen:]
- General Availability (Worldwide, GCC, GCCH): Rollout begins in late April 2026.
[How this affects your organization:]
Who is affected:
- Users who create agents using Agent Builder in Microsoft 365 Copilot
- This feature is available to those using Copilot Chat (Basic) as well as Microsoft 365 Copilot (Premium).
What will happen:
- Users can develop agents using natural language prompts, with guidance provided through an intuitive creation experience.
Screenshot 1: The Agent Builder landing page now shows templates and a list of existing agents, making it easier to start or reuse an agent: 
Screenshot 2: The Describe and Configure panes are displayed side by side: 
- Updates in the Describe pane automatically reflect in the configuration in real time.
- The configuration pane highlights what changed and why.
- Users can review how instructions evolve over time by selecting Show changes.
- Testing an agent is now accessed through a Try it toggle, allowing users to switch between configuring and testing before publishing.
- The feature is enabled by default and does not require admin configuration.
There are no changes to:
- How agents work once published
- Admin policies, controls, or permissions
- Existing agents or configurations
[What you can do to prepare:]
No action is required.
You may consider the following optional steps:
- Inform helpdesk staff that Agent Builder has a refreshed creation layout.
- Update internal training or documentation if you reference screenshots or step-by-step agent creation guidance.
Learn more: Build agents by using Agent Builder in Microsoft 365 Copilot | Microsoft Learn [Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| Create and edit SharePoint pages with Copilot-powered AICategory:SharePoint OnlineNummer:MC1282683Status:stayInformed | [Introduction] We are introducing Create and edit SharePoint pages with Copilot-powered AI, a new authoring experience that helps page editors plan, create, and refine SharePoint pages using natural language prompts. This feature reduces the time and effort required to build high-quality pages by allowing authors to generate and edit content, layouts, and web parts directly through an AI-assisted editing panel, grounded in their organization’s existing Microsoft 365 content. [When this will happen] - Targeted Release: We began rolling out in early April 2026 and expect to complete by mid-April 2026.
- General Availability (Worldwide): We will begin rolling out in early May 2026 and expect to complete by early June 2026.
[How this affects your organization] Who is affected - SharePoint page editors in Microsoft 365 tenants
- Only users assigned a Microsoft 365 Copilot license
- Production tenants (not GCC or Gallatin)
What will happen - Page editors with a Copilot license will see a new AI authoring panel automatically open when editing SharePoint pages:
- Users can:
- Generate new page sections using natural language prompts:
- Edit existing text, layouts, and web parts through chat-based instructions.
- Attach Microsoft 365 files as grounding context for better AI-generated results:
- AI-generated changes are inserted directly into the page and visually highlighted:
- Users can switch between AI-assisted editing and standard manual editing at any time:
- Chat history persists for the duration of the editing session unless manually cleared:
- This feature is enabled by default for eligible users with Copilot licenses.
[What you can do to prepare] No action is required to prepare for this change. Recommended actions: - Inform SharePoint page authors about the new AI-assisted editing experience.
- Update internal documentation or training materials if you provide guidance on SharePoint authoring.
- Ensure Copilot license assignments align with who should have access to AI-powered page creation.
[Compliance considerations] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed (for example, documents or page content)? | Yes. Copilot uses existing SharePoint page content and user-selected Microsoft 365 files (such as documents) as grounding context to generate or edit page sections. Content is processed at the time of generation to produce suggestions and changes directly in the page editor. | | Does the change introduce or significantly modify AI or agent capabilities that interact with customer data? | Yes. This change introduces a Copilot-powered AI authoring experience in SharePoint. The AI assists users by generating and editing page content, layouts, and web parts based on prompts and selected Microsoft 365 content. | | Does the change provide users a new way of interacting with generative AI? | Yes. Page editors with a Copilot license can interact with generative AI directly within the SharePoint page editing experience using natural language chat prompts to plan, create, and modify content. | | Does the change include an admin control, and can it be controlled through Entra ID group membership? | Yes. Access to the feature is governed by Microsoft Copilot license assignment. Only users assigned a Copilot license can access the AI authoring panel. There is no additional tenant-level toggle specific to this feature. | | Does the change allow users to enable or disable the feature themselves? | Yes. While the feature is available by default for Copilot-licensed users, users can choose when to use AI during page editing and can switch between AI-assisted editing and standard manual editing at any time. |
|
| Microsoft Copilot Studio – UPDATE – Classic agent creation experience in TeamsCategory:Microsoft Copilot (Power Platform)Nummer:MC1282727Status:stayInformed | In a previous communication, MC1274562, we announced that the classic agent creation experience in the Microsoft Copilot Studio (formerly Power Virtual Agents) app for Teams would be retired beginning April 1, 2026.
Due to implementation issues, we are reevaluating the timeline for this change.
At this time, existing Office and Microsoft 365 customers can continue to access and use the Microsoft Copilot Studio app in Teams to create and edit agents.
We will provide an updated timeline once a confirmed retirement date is established. The updated timeline will allow customers sufficient time to make any necessary adjustments prior to this change.
How does this affect me?
There is no immediate change to your current experience. Admins and users can continue to access and use the Microsoft Copilot Studio app in Teams.
What action do I need to take?
No action is required at this time. |
| Microsoft Dataverse – Service Update 9.2.26042.00000 for EURCategory:Microsoft DataverseNummer:MC1283341Status:stayInformed | We have a minor service update planned for your Microsoft Dataverse environment hosted in EUR.
This service update will occur within your region’s scheduled maintenance timeline, on the scheduled date listed for Microsoft Dataverse.
How does this affect me?
The version number for your Microsoft Dataverse environment will update to version 9.2.26042.00000 or higher.
There is no expected degradation to service performance or availability, however, during this maintenance window users may see short, intermittent impact such as transient SQL errors or a redirect to the login screen.
What action do I need to take?
This message is for awareness and no action is required. |
| Interim guidance for Egypt DST changes 2026Category:WindowsNummer:MC1283618Status:preventOrFixIssue | For Windows devices in Egypt, a workaround is available for an issue affecting Daylight Saving Time (DST). Between April 24 and April 30, 2026, calendar events and meeting times in Egypt will appear off by one hour only for Windows Server 2016. This is due to a calendar edge case: a five-week April in 2026. Clocks will be correctly set to Egypt DST time zone on May 1, 2026, without any further intervention. If needed, a temporary workaround is available for the affected week. When will this happen: - The workaround is available today.
- April 24-30, 2026: Affected devices might see calendar events off by an hour.
- May 1, 2026: Clocks will be correctly set to Egypt DST time zone without any further intervention, whether you use the workaround or not.
How this will affect your organization: If your organization has devices affected by this issue and you don’t apply the workaround, the impact is as follows: - Clocks will not be advanced by an hour at 12:00 a.m. on April 24, 2026, for the Egypt time zone until 12:00 a.m. on May 1, 2026.
- Clocks will be automatically advanced by an hour at 12:00 a.m. on May 01, 2026, for the Egypt time zone.
If you apply the workaround, you can avoid this issue during the last week of April 2026. What you need to do to prepare: No action is needed if you don’t use Windows Server 2016, and all other devices use in-support versions of Windows. If your devices are affected, you can use a temporary registry setting workaround. No action is needed after May 1, 2026. On that date, all in-support systems will show the correct Egypt DST time automatically. Additional information: |
| First channel in new Microsoft Teams will default to threaded conversation layoutCategory:Microsoft TeamsNummer:MC1283811Status:stayInformed | Introduction
We’re updating the default conversation layout for the first channel created in new Microsoft Teams. Starting in May 2026, the first channel in any newly created team will default to the Threaded (conversation) layout instead of Posts. This change aligns the first channel experience with the standard default for all newly created channels, helping teams organize conversations more effectively from the start and improving discussion clarity for project-based collaboration.
When this will happen:
- General Availability (Worldwide): Rollout will begin in early May 2026 and is expected to complete by early May 2026.
How this affects your organization:
Who is affected:
- Team owners creating new Microsoft Teams
- End users participating in newly created teams
- Microsoft 365 administrators managing Teams governance and user adoption
What will happen:
- The first channel created automatically during team creation will default to the Threaded layout.
- This change applies only to newly created teams after rollout.
- Existing teams and their channels will remain unchanged.
- Team owners can switch the first channel layout from Threaded to Posts at any time after creation.
- The feature is enabled by default and requires no admin configuration.
- There is no impact to existing Teams policies or channel moderation settings.
What you can do to prepare:
- Inform your helpdesk and Teams champions that new teams will start with the Threaded layout in the first channel.
- Update internal Teams onboarding or governance documentation if you reference default channel behavior.
- Educate team owners that they can change the channel layout after team creation if Posts are preferred.
Compliance considerations:
| Area |
Explanation |
| Does the change provide a new way of communicating between users, tenants, or subscriptions? |
The change modifies the default conversation layout for the first channel created in newly provisioned Microsoft Teams from Posts to Threaded. While this does not introduce a new communication modality, it changes the default way conversations are structured and presented within the first channel of newly created teams, which may affect how users organize and review discussions. |
| Does the change allow a user to enable and disable the feature themselves? |
Team owners can change the conversation layout of the channel after team creation. This is a per-channel user experience setting and is not controlled through tenant-level administrative policy. |
| Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.)? |
While no changes are made to how customer data is stored or retained, the change to a threaded layout as the default in newly created teams may influence how channel message content is displayed and interacted with by users within the Teams client. |
| Does the change include an admin control and, can it be controlled through Entra ID group membership? |
The default layout behavior is applied automatically at team creation and there is currently no tenant-level administrative policy or Entra ID group-based control available to manage this behavior. |
|
| Microsoft Teams admin center: Events license management for Attendee Capacity Pack licensesCategory:Microsoft TeamsNummer:MC1283813Status:stayInformed | [Introduction]
We’re introducing new license management capabilities for Microsoft Teams Events in the Teams admin center (TAC). This update provides admins with a centralized experience to discover, assign, and manage Attendee Capacity Pack licenses for event organizers from a single location. This experience aligns with existing Teams add-on license management patterns and helps admins proactively manage licensing needs for upcoming events. ]When this will happen]
General Availability (Worldwide, GCC): Rollout will begin in late April 2026 and is expected to complete by early May 2026.
[How this affects your organization]
Who is affected:
- Admins managing Microsoft Teams Events licensing in the Teams admin center
- Organizations that have purchased at least one Attendee Capacity Pack license
What will happen:
- Admins can discover Teams Events Attendee Capacity Pack licenses in a dedicated add-on licensing experience in TAC.
- Admins can assign, reassign, or revoke Attendee Capacity Pack licenses for event organizers.
Screenshot: Teams admin center > Teams Events: Attendee Capacity Pack license management experience:  >
- License assignment status will be visible at both the user and tenant levels.
- Admins removing a license will receive impact warnings if the organizer has upcoming events that may be affected.
- Admins can view upcoming events that could be impacted prior to removing a license.
- This feature is available by default when eligible licenses are present.
- No policy changes are required.
- There is no impact to user workflows.
[What you can do to prepare]
- No action is required before rollout.
- Review your current Teams Events licensing configuration.
- Update internal documentation and training materials as needed.
- Communicate this change to your helpdesk and event organizers.
Learn more about managing Attendee Capacity Pack licenses in TAC: Manage Attendee Capacity Pack licenses | Microsoft Learn
[Compliance considerations]
No compliance considerations identified, review as appropriate for your organization. |
| Microsoft Teams: Meeting organizers can automatically start transcription without recordingCategory:Microsoft TeamsNummer:MC1283816Status:stayInformed | [Introduction] Meeting organizers can now select Transcribe only as an automatic meeting option in Microsoft Teams. This setting starts transcription automatically when the meeting begins—without creating a recording—providing more granular control in meetings where recording is restricted due to compliance or privacy policies while still supporting accessibility, Microsoft Copilot, and Intelligent Recap. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web.
Screenshot: Updated meeting options showing Off, Record and transcribe, and Transcribe only: 
[When this will happen:]
- Targeted Release: We will begin rolling out in late April 2026 and expect to complete by late April 2026.
- General Availability (Worldwide): We will begin rolling out in early May 2026 and expect to complete by mid-May 2026.
[How this affects your organization:]
Who is affected:
- Microsoft Teams meeting organizers with transcription enabled through meeting policies
- Admins managing Teams meeting and recording policies
What will happen:
- Previously, the Record and transcribe automatically meeting option was a single on/off toggle that always started both recording and transcription together. This option will be replaced with a list of automatic meeting settings when scheduling a meeting:
- Off: No automatic recording or transcription (default)
- Record and transcribe: Both recording and transcription start automatically (same as previous automatic recording behavior)
- Transcribe only: Only transcription starts automatically; no recording is created
- When Transcribe only is selected, the meeting transcript is generated and available after the meeting without any recording artifact being stored.
- The meeting policy
AllowTranscription must be set to On for the organizer to see the Transcribe only option.
- If the Who can record and transcribe meeting option is set to No one, all automatic transcription options (including Transcribe only) are forced Off.
- Standard Teams transcription (included in Microsoft 365 E3/E5) is sufficient for the Transcribe only option. No additional license is required.
[What you can do to prepare:]
- No administrative action is required before the rollout.
- Review your organization’s meeting policies to ensure
AllowTranscription is enabled for users who require this capability.
- Update internal documentation or training materials to reflect the new meeting option.
- Notify meeting organizers about the availability of the Transcribe only setting.
Learn more: Manage meeting transcription and captions in Microsoft Teams | Microsoft Learn
[Compliance considerations:]
| Area |
Explanation |
| Introduces or modifies AI/ML capabilities interacting with customer data |
Transcripts created without recordings can be used by Microsoft Copilot and Intelligent Recap to generate meeting insights where recording is restricted. |
| Admin control available and assignable through Entra ID group membership |
Admins can manage availability through Teams meeting policies (AllowTranscription), which can be assigned to users or groups. |
|
