| (Updated) Microsoft Teams: Apps now supported in Private ChannelsCategory:Microsoft TeamsNummer:MC1197145Status:stayInformed | Updated July 8, 2026: We have updated the timeline and added documentation. This feature is now available. Thank you for your patience. Introduction We’re excited to announce that Microsoft Teams now supports apps in Private channels. This update enables richer collaboration scenarios across teams and organizations by allowing users to add and use apps—including bots, tabs, and message extensions—directly within Private channels. This change aligns with customer feedback requesting more consistent and flexible app experiences across collaboration spaces. Support for apps in Private Channels follows the same model as that for shared channels, ensuring a unified experience for users and developers. For organizations using custom line-of-business (LOB) apps, developer updates are required to ensure private and shared channel compatibility.
This message is associated with Roadmap ID 518215 and applies to Teams for Windows desktop and Teams for Mac desktop.
When this will happen:
- Targeted release: Rollout begins mid-January 2026, and we expect to complete by late June 2026 (previously late January).
- General availability (Worldwide): This feature is now available.
How this affects your organization:
Who is affected:
- All Microsoft Teams users who participate in Private Channels
- Admins managing Teams app policies
- Developers maintaining Teams apps
What’s changing:
- Apps can now be added to Private Channels. Previously, only a limited set of tabs were supported.
- This feature is available by default.
- All apps marked to work in Private and Shared Channels will be available.
- Channel owners or members can add apps to a Private Channel, with new governance and consent controls.
- A new channel setting allows owners to control who can add apps.
- Apps must be explicitly added to each channel; installing at the team level will no longer apply to Shared or Private Channels.
Screenshot 1: Apps must be added per channel. Users are prompted for consent when interacting with an app that hasn’t been added. Apps are available through all standard discovery entry points. 
Screenshot 2: Manage apps in your channels from the new Apps tab in Manage channel settings. 
- Guest users can use supported apps depending on app and admin settings.
- Only apps updated by developers to support Private Channel functionality and allowed by admins will be available.
- Support for apps in Private Channels will follow the same model and require similar updates.
- Guidance is available now so organizations can work with custom LOB app developers to plan required updates.
What you can do to prepare:
Admins: - Review custom LOB apps used in team and channel scenarios and coordinate with app developers to complete the required updates for private/shared channel compatibility.
- Update internal documentation.
Developers: Compliance considerations:
| Compliance Area | Explanation |
|---|
| Does the change store new customer data, if so, where, and is the data cached or permanently stored? | Apps added to Private Channels may store channel-specific data such as membership, settings, and user interactions. Storage location depends on the app’s architecture and may include Microsoft 365 or third-party services. |
| Does the change alter how existing customer data is processed, stored, or accessed? | Apps now operate at the channel level, not the team level. This changes how data access and permissions are scoped, requiring updates to app manifests and use of channel-specific APIs. |
| Does the change provide a new way of communicating between users, tenants, or subscriptions? | Apps (including bots and message extensions) within Private Channels enable new interaction paths among channel members, including guest users, depending on admin and app settings. |
| Does the change modify, interrupt, or disable any of the following capabilities (Purview)? | Apps must be explicitly added per channel, which may affect how DLP policies, audit logging, and eDiscovery apply. Admins should validate app behavior in Private Channels to ensure compliance. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Admins must review app usage and permissions at the channel level. Monitoring tools may need updates to reflect app activity in Private Channels. |
| Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? | Apps in Private Channels may store user interactions and data that must be considered in GDPR-related requests. Admins and developers should ensure data handling aligns with privacy obligations. |
| Does the change include an admin control and, can it be controlled through Entra ID group membership? | Admins can manage app permissions and availability via Teams app policies and channel settings. Entra ID group membership may be used to scope access. |
| Does the change allow a user to enable and disable the feature themselves? | Channel owners can control who can add apps, and users can interact with apps once added, subject to consent prompts and admin policies. |
|
| (Updated) Microsoft 365 Copilot: Draft and send Outlook email directly in Copilot ChatCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1247637Status:stayInformed | Updated July 7, 2026: We have updated the content. Thank you for your patience. [Introduction] We’re enhancing Microsoft 365 Copilot Chat by enabling users to draft, edit, and send Outlook email directly within Copilot Chat. When Microsoft 365 Copilot identifies an email‑writing intent, it will open an embedded Outlook compose form. This improvement reduces context switching and streamlines everyday communication workflows. [When this will happen] - General Availability (Worldwide): Rollout will begin in early May 2026 (previously late March) and is expected to complete by early June 2026 (previously late April).
- Not available: This feature is not yet available in DonMT environments
[How this will affect your organization] Who is affected - Users licensed for Microsoft 365 Copilot
- Users with Exchange Online mailboxes
- Users accessing Copilot Chat on desktop (“big screen”)
What will happen - When users ask Copilot to draft an email, an embedded Outlook compose form will appear directly within Copilot Chat:
- Users will be able to:
- Edit the email content
- Modify recipients
- Send the email from within Copilot Chat
- Open the draft in Outlook to continue editing
- The feature will be on by default for all eligible users.
- Availability:
- Available: Copilot Chat desktop app
- Not available: Copilot Chat mobile app or chat sidebar
- Existing Outlook and Exchange Online policies—including DLP—continue to apply.
- No admin configuration changes or new controls are introduced.
Note: Access to this feature requires an active Microsoft 365 Copilot license. [What you can do to prepare] No action is required. You may choose to: - Inform your helpdesk and end users about this new email‑drafting experience in Copilot Chat.
- Update internal documentation if you describe Copilot Chat workflows.
- Review which users in your organization are licensed for Microsoft 365 Copilot.
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. |
| (Updated) Microsoft 365 Copilot: Intelligent Summaries in Copilot DashboardCategory:Microsoft Viva
Microsoft Copilot (Microsoft 365)Nummer:MC1266912Status:stayInformed | Updated July 7, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Intelligent summaries in Copilot Dashboard help you quickly understand what’s driving Copilot adoption in your organization. These AI‑generated insights highlight key usage trends, areas of success, and opportunities where focused attention can accelerate value. Suggested prompts guide deeper exploration of underlying drivers and adoption patterns. This message is associated with Microsoft 365 Roadmap ID 557681. [When this will happen] - General Availability (Worldwide): Rollout will begin in mid-August 2026 (previously early July) and is expected to complete by mid-September 2026 (previously late July).
[How this will affect your organization] Who is affected - Admins using the Microsoft 365 Copilot Dashboard in Microsoft Viva and Microsoft 365
What will happen - Intelligent summaries will appear automatically in the Copilot Dashboard:
- Admins will see AI‑generated insights that highlight adoption trends and key usage patterns.
- Suggested prompts will be available to help admins drill into specific drivers and areas of opportunity.
- No configuration changes are required; the feature is on by default for eligible tenants.
- Existing admin controls and permissions remain unchanged.
- There is no user workflow impact.
[What you can do to prepare] No action is required before rollout. If helpful for your organization, you may: - Notify helpdesk or training teams about the new summaries.
- Update internal documentation that references the Copilot Dashboard.
- Review updated online documentation, which will be refreshed as rollout begins in late April.
- If you choose not to use this feature, you can roll back by disabling intelligent summaries using available admin controls.
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. |
| Microsoft Power Platform governance and administration – Safety GraderCategory:Power PlatformNummer:MC1419786Status:stayInformed | We are announcing the ability to evaluate AI responses using configurable safety graders to identify unsafe or policy-violating outputs in Microsoft Power Platform governance and administration. This feature will reach public preview on July 15, 2026.
How does this affect me?
Admins will be able to configure specific safety criteria to evaluate AI responses prior to them being sent to identify policy-violating outputs. Once configured, the Safety Grader will be able to do the following: - Evaluate responses against safety criteria.
- Detect unsafe or undesirable outputs.
- Combine safety evaluations with other graders.
- Provide detailed explanations and evidence supporting the evaluation for each result.
What action do I need to take?
This message is for awareness, and no action is required. |
| PowerPoint for the web: One‑click “Review Presentation” and “Visualize Slide” Copilot skills in the ribbonCategory:Microsoft 365 for the web
Microsoft Copilot (Microsoft 365)
Microsoft 365 Copilot ChatNummer:MC1419795Status:stayInformed | [What and Why:]
We are introducing one-click Copilot entry points in PowerPoint for the web through two new ribbon skills: Review Presentation (Review tab) and Visualize Slide (Design tab). These capabilities make it easier for users to quickly access Copilot-powered assistance directly within their workflow—helping improve presentation quality, accelerate content refinement, and enhance visual storytelling. This update supports personal and team productivity by turning intent into results with minimal friction.
[Rollout Schedule:]
- General Availability (Worldwide): Rollout began in late June 2026 and is expected to complete by early July 2026
[Impact on Your Organization:]
Who is affected: - Users with access to Copilot in PowerPoint for the web
- Admins managing Microsoft 365 Apps and Copilot configurations
Platforms/Services: PowerPoint for the web
What will happen:
- Users will see:
- A new “Review Presentation” button in the Review ribbon tab.
- A new “Visualize Slide” button in the Design ribbon tab.
- These provides one-click activation to Copilot capabilities.
- Visualize Slide requires image generation capability enabled by admin.
- Feature is available when prerequisites are met; no additional setup required.
[Action Required/Recommendations:]
No action is required if your organization already uses Copilot and image generation is enabled. If you want users to fully benefit from this feature:
- Confirm Copilot licensing for intended users.
- Enable image generation in Microsoft 365 Apps admin center.
- Communicate the update to users.
- Update internal documentation and training materials.
Learn more: Edit with Copilot in PowerPoint | Microsoft Support [Compliance considerations:]
| Compliance Area |
Explanation |
| Introduces AI/ML capabilities interacting with customer data |
These features are Copilot-powered and analyze slide content to provide feedback and generate visuals, which involves AI processing of customer presentation data. |
| New way for users to interact with generative AI |
Users can directly trigger Copilot capabilities from the ribbon to review presentations and generate slide visuals with one click. |
| Admin control available |
Use depends on Copilot licensing and enabling image generation via the Microsoft 365 Apps admin center, indicating partial administrative control. |
|
| Microsoft Purview | Data Loss Prevention – Extend Purview data security to the network layer via Entra GSA integrationCategory:Microsoft PurviewNummer:MC1419797Status:planForChange | [What and Why:]
Extend Microsoft Purview data security controls to the network layer by integrating with Entra Internet Access. This integration helps organizations detect and protect sensitive data in text, prompts, and AI interactions by enabling inspection at the network layer, enforcing actions based on DLP policies, and identifying risky user activity through Insider Risk Management. It also helps prevent sensitive data from being shared with untrusted cloud applications—including generative AI platforms, social media, and collaboration tools—across browsers, apps, APIs, and add-ins, while managing alerts and incidents through Purview and Microsoft Defender. For more information, refer to Protect sensitive data in motion across SaaS and AI apps with Microsoft Purview and Microsoft Entra. This message is associated with Microsoft 365 Roadmap ID 566528.
[Rollout Schedule:]
- Public Preview: Beginning early July 2026; expected to complete by late July 2026
- General Availability (Worldwide): Beginning late September 2026; expected to complete by late October 2026
[Impact on Your Organization:]
Who is affected:
- Purview administrators
- Security administrators
- Compliance administrators
- Entra Global Secure Access administrators
Platforms/Services:
- Microsoft Purview
- Microsoft Purview DLP
- Microsoft Entra Internet Access
- Microsoft Entra Global Secure Access
- Microsoft Defender
What will happen:
- The integration will become available automatically in eligible tenants as rollout completes.
- Administrators can create policies that inspect network traffic using Entra Internet Access.
- Organizations can apply Purview classifications and DLP controls to network-layer traffic.
- Sensitive text, prompts, and files can be inspected and protected when transmitted to supported cloud and AI services.
- Administrators can audit or block policy violations based on sensitive information types, sensitivity labels, or user risk levels.
- Alerts and incidents can be surfaced through Microsoft Purview and Microsoft Defender.
- Existing inline web traffic policies and network-based Purview protections continue to function without interruption.
- The capability is administrator-configured and is not enabled for enforcement until policies are created and deployed.
- Support extends to unmanaged AI applications, cloud storage providers, webmail, social media, forms, and other internet destinations supported by the service.
[Action Required/Recommendations:]
No immediate action is required before rollout. Recommended preparation activities:
- Review whether your organization uses or plans to deploy Microsoft Entra Internet Access.
- Evaluate licensing and prerequisite requirements for Microsoft Purview DLP and Entra Internet Access.
- Review current DLP policies and determine whether network-layer protection scenarios should be added.
- Identify unmanaged AI applications and cloud services that may require monitoring or policy enforcement.
- Review pay-as-you-go billing requirements associated with Microsoft Purview Network Data Security.
- Validate existing TLS inspection and Global Secure Access deployment readiness if planning to use the feature.
- Inform security operations and compliance teams of the upcoming capability.
Learn more about the solution (including prerequisites):
[Compliance Considerations:]
| Area |
Explanation |
| Data processing |
Microsoft Purview DLP inspection is extended to the network layer through Entra Internet Access integration. Network traffic containing files, text, and AI interactions can be intercepted, inspected, classified, and evaluated against Purview policies before data is sent to external cloud services. |
| AI/ML capabilities |
Organizations can inspect prompts and responses involving generative AI services and apply Purview classifications, DLP policies, and Insider Risk Management controls to AI-related interactions at the network layer. |
| Communication methods |
The feature does not create new communication channels, but it adds monitoring and enforcement capabilities for communications and content exchanges with external AI platforms, cloud services, collaboration tools, and social media applications. |
| AI user interaction |
The primary purpose is governance and protection rather than enabling new AI experiences. However, organizations may allow or restrict AI interactions differently based on newly available network-layer DLP controls. |
| DLP enforcement |
Existing Purview DLP capabilities are expanded to include network-layer enforcement through Entra Internet Access. Organizations can block, audit, or monitor sensitive data transfers to external destinations using existing DLP policy constructs. |
| Information protection |
Existing sensitivity labels and sensitive information types can be used for inspection and enforcement against network traffic, extending the scope of existing protection controls. |
| Conditional Access |
Administrators may need to create or update Conditional Access policies to apply Global Secure Access security profiles that enforce content filtering and network inspection policies. |
| Audit logging |
Additional monitoring, alerts, incidents, traffic logs, and investigation data become available through Purview, Defender, and Global Secure Access logging experiences. |
| Compliance reporting |
Administrators gain new visibility into network-layer data movements, AI interactions, DLP alerts, incidents, investigations, and risky behavior through Purview and Microsoft Defender portals. |
| Third-party services |
The solution can inspect interactions with external generative AI applications, social media services, collaboration platforms, cloud storage providers, and other third-party internet destinations through Entra Internet Access controls. |
| Admin controls |
Administrators must configure content filtering, DLP policies, security profiles, and associated Conditional Access assignments. User targeting can be managed through standard Entra ID group-based assignments. |
|
| Microsoft Teams Rooms: Identify in-room participants with IntelliFrame people labelsCategory:Microsoft TeamsNummer:MC1419798Status:planForChange | [What and Why:]
We’re introducing IntelliFrame people labels in Microsoft Teams Rooms on Windows to improve meeting clarity and inclusivity for remote participants. When enabled, this feature identifies in-room participants by name and displays a contact card, helping remote attendees easily recognize speakers and follow conversations.
This enhancement supports better hybrid meeting experiences by connecting in-room and remote participants more effectively, improving collaboration and productivity. This message is associated with Microsoft 365 Roadmap ID 566700.
[Rollout Schedule:]
- General Availability (Worldwide, GCC): Beginning early September 2026; expected to complete by late September 2026
[Impact on Your Organization:]
Who is affected:
- Organizations using Microsoft Teams Rooms on Windows with Teams Rooms Pro licenses
- In-room participants who have enrolled in voice and face recognition (People Recognition)
Platforms/Services:
- Microsoft Teams
- Teams Rooms on Windows devices
- Supported intelligent camera hardware
What will happen:
- IntelliFrame will display name labels under identified in-room participants’ video feeds.
- Remote participants can select a label to view a contact card with organizational details.
- The feature is enabled automatically when prerequisites are met.
- Existing Teams meeting policies for voice and face enrollment are honored.
- Participants without enrolled profiles will appear without labels.
- No change occurs if voice and face enrollment is disabled in your organization.
[Action Required/Recommendations:] No action is required to enable this feature. To maximize value, administrators may: - Review and confirm Teams Rooms devices:
- Ensure devices are licensed with Teams Rooms Pro.
- Verify use of supported intelligent cameras.
- Review and update meeting policies:
- Allow enrollment:
Set-CsTeamsMeetingPolicy -EnrollUserOverride Enabled. - Enable name display in rooms:
Set-CsTeamsMeetingPolicy -RoomPeopleNameUserOverride On.
- Encourage users to enroll in voice and face recognition: Teams > Settings > Recognition.
- Update internal documentation and helpdesk guidance.
- Notify users about this capability to drive awareness and adoption.
To disable IntelliFrame people labels, administrators can:
-
Turn off in-room name display (labels stop; other IntelliFrame framing unaffected):
Set-CsTeamsMeetingPolicy -RoomPeopleNameUserOverride Off
-
Block voice and face enrollment entirely (no one can be identified by name):
Set-CsTeamsMeetingPolicy -EnrollUserOverride Disabled
-
Individual users can opt out anytime by removing their profile in Teams > Settings > Recognition.
Learn more: [Compliance considerations:]
| Compliance Area |
Impact |
| Introduces or modifies AI/ML capabilities |
Uses AI-based biometric identification (voice and face profiles) to identify in-room participants. Identification occurs only for users who have consented and completed People Recognition enrollment. |
| Stores new customer data |
This feature does not create new data; it relies on existing voice and face profiles from People Recognition enrollment, governed by the organization’s current configuration. |
| Alters processing of existing customer data |
Participant identity data is processed differently when recognition is enabled. |
| Provides new way of communicating between users |
Labels and contact cards enhance visibility of in-room participants for remote users. |
| Adds or changes admin controls |
Controlled via Teams meeting policies (EnrollUserOverride and RoomPeopleNameUserOverride). |
| Allows users to enable/disable the feature |
Users can enroll or opt out of voice and face profiles in Teams settings. |
|
| Configurable recovery window for Microsoft 365 BackupCategory:Microsoft 365 suiteNummer:MC1419799Status:stayInformed | [What and Why:]
We’re introducing configurable recovery window for Microsoft 365 Backup, allowing administrators to define backup recovery windows between 3 months and 2 years at the policy level. Previously, recovery window was fixed at 1 year. This enhancement provides greater flexibility to align data protection practices with organizational compliance requirements, cost considerations, and business continuity strategies—improving control over backup lifecycle management. This message is associated with Microsoft 365 Roadmap ID 481834.
[Rollout Schedule:]
- Public Preview (Worldwide): Beginning late July 2026; expected to complete by early August 2026
- General Availability (Worldwide): Beginning late July 2026; expected to complete by early August 2026
[Impact on Your Organization:]
Who is affected: Microsoft 365 administrators managing Microsoft 365 Backup policies
Platforms/Services:
- Microsoft 365 admin center (web)
- Microsoft 365 Backup
What will happen:
- Admins can configure recovery window per backup policy between 3 months and 2 years.
- The default recovery window remains 1 year unless changed.
- Existing policies will not be modified automatically.
- Recovery window can be set during policy creation or editing.
- The feature is enabled by default but requires manual configuration to change settings.
- Reducing recovery window on an existing policy will:
- Permanently delete backup data outside the new recovery window.
- Apply deletion after a defined grace period.
[Action Required/Recommendations:] No immediate action is required before rollout.
After rollout, we recommend:
- Review existing Microsoft 365 Backup policies to confirm if the default 1-year recovery window meets your needs.
- Evaluate whether shorter or longer recovery window aligns with your compliance and recovery objectives.
- Inform backup and IT administrators about this new capability.
- Plan carefully before reducing recovery window to avoid unintended permanent data loss.
- Update internal documentation and governance procedures if applicable.
To configure recovery window:
- Go to the Microsoft 365 admin center: Open Microsoft 365 admin center
- Navigate to Microsoft 365 Backup
- Select a backup policy
- Open “Update recovery window”
- Set the recovery window (3 months to 2 years)
- Review and confirm changes
[Compliance considerations:]
| Consideration | Explanation |
|---|
| Does the change alter how existing customer data is processed, stored, or accessed? | Recovery window duration for backup data is configurable. Shortening it may result in permanent deletion of backup data beyond the new window after a grace period. |
| Does the change modify retention policies, holds, or deletion workflows (Purview)? | While separate from Purview retention, this introduces configurable backup recovery window behavior that directly impacts data lifecycle and deletion timing of the backups. |
| Does the change include an admin control? | Admins can configure recovery window per backup policy in the Microsoft 365 admin center. |
|
| SharePoint button web part: Add custom Copilot in SharePoint prompts or start Power Automate flowsCategory:SharePoint Online
Microsoft Copilot (Microsoft 365)Nummer:MC1419800Status:planForChange | [What and Why:]
Microsoft is expanding the capabilities of the SharePoint Button web part beyond static hyperlinks. Organizations can now create buttons that either launch a predefined prompt in Copilot for SharePoint (for users licensed for Microsoft 365 Copilot) or initiate a Power Automate flow. This enhancement supports Personal and Team Productivity and Business Process Automation by helping users access AI-powered experiences and workflow automation directly from SharePoint pages.
[Rollout Schedule:]
- Targeted Release (Worldwide): Beginning in late July 2026; expected to complete by late July 2026
- General Availability (Worldwide): Beginning in late July 2026; expected to complete by mid-August 2026
- General Availability (GCC): Beginning in late July 2026; expected to complete by late August 2026
- General Availability (GCC High): Beginning in late July 2026; expected to complete by early September 2026
[Impact on Your Organization:]
Who is affected:
- SharePoint page owners and site editors.
- Users with Microsoft 365 Copilot licenses.
- Users authorized to run Power Automate flows.
Platforms/Services:
- SharePoint Online
- Microsoft 365 Copilot
- Power Automate
- Web
What will happen:
- Existing Button web part links will continue to function without changes.
- Page authors will be able to configure a Button web part to launch a predefined Copilot in SharePoint prompt.
- Page authors will be able to configure a Button web part to initiate a Power Automate flow using a Flow ID.
- Copilot in SharePoint prompt buttons will be available only to users who have a valid Copilot license.
- Power Automate flow buttons can be used by authorized users regardless of Copilot licensing.
- The feature will be available by default once released; no migration of existing button links is required.
- No changes are made to existing Button web part configurations.
[Action Required/Recommendations:]
No administrative action is required.
Recommended actions: - Review SharePoint governance and page authoring guidance before rollout.
- Inform SharePoint site owners and content authors about the new Button web part capabilities.
- Communicate to licensed Copilot users that custom Copilot in SharePoint prompt buttons can be added to SharePoint pages.
- Evaluate whether predefined Copilot in SharePoint prompts could streamline common employee workflows and knowledge discovery scenarios.
- Review Power Automate flows that may benefit from direct launch from SharePoint pages.
- Update internal SharePoint training materials or documentation if you provide guidance on page authoring.
- Review licensing requirements to ensure users expected to use Copilot in SharePoint prompt buttons have appropriate Copilot licenses assigned.
Learn more: Use the Button web part | Microsoft Support (will be updated before rollout) [Compliance Considerations:]
| Compliance Area |
Explanation |
| Introduces or significantly modifies AI/ML or agent capabilities that interact with or provide access to customer data |
The update introduces a new capability that allows SharePoint page authors to create Button web parts that launch predefined prompts in Copilot for SharePoint. This provides a new entry point for users with a Copilot license to interact with AI experiences grounded in organizational content and permissions. |
| Provides end users a new way of interacting with generative AI |
Users with a Microsoft 365 Copilot license can invoke predefined Copilot in SharePoint prompts directly from SharePoint pages by selecting a configured button, creating a simplified and guided generative AI experience. |
| Includes an admin control and can be controlled through Entra ID group membership |
No new dedicated admin control is described in the announcement. However, access to Copilot experiences continues to depend on existing Microsoft 365 Copilot licensing, permissions, and any organizational controls already used to govern Copilot access, which may include Entra ID group-based license assignment. |
| Allows a user to enable or disable the feature themselves |
SharePoint page owners and authors can choose whether to configure Button web parts as traditional links, Copilot in SharePoint prompt buttons, or Power Automate flow launch buttons on pages they manage. |
|
| Microsoft Viva Insights: Is Active filter no longer applied by default in new Advanced Insights queriesCategory:Microsoft Viva
Microsoft Copilot (Microsoft 365)Nummer:MC1419801Status:stayInformed | [What and Why:]
Microsoft is updating how the Is Active filter works in Viva Insights Advanced Insights. Today, the filter is automatically applied to certain new Custom Query – Person queries. Beginning in August 2026, Is Active will no longer be selected by default. Instead, analysts must explicitly choose it when they want to limit results to active users.
This change improves transparency and predictability in analytics by preventing users from unintentionally excluding populations from query results. It is particularly valuable when analyzing Copilot metrics, where default filtering could lead to misunderstandings about adoption and usage. Existing queries and Power BI templates remain unchanged, protecting current reporting and business processes. [Rollout Schedule:]
- General Availability (Worldwide): Rollout begins in early August 2026; expected to complete by mid-August 2026.
[Impact on Your Organization:]
Who is affected:
- Viva Insights Advanced Insights users.
- Analysts and report authors creating new Custom Query – Person queries.
- Organizations using Copilot metrics and/or behavioral data.
- A Microsoft 365 Copilot (Premium) license is required to use this feature.
Platforms/Services:
- Microsoft Viva Insights
- Advanced Insights
- Power BI templates
- Copilot metrics reporting
- Behavioral analytics reporting
What will happen:
-
New queries:
-
Copilot-only Queries (no behavioral data):
- The Is Active option will be disabled in the query builder.
- Users will receive an informational message: “Is Active filtering is not applicable to Copilot-metrics and isActive filter will not be applied to overall report “
- This prevents confusion because the filter does not have a meaningful impact without behavioral data.
-
Copilot + behavioral Queries
- If a query has both Copilot and behavioral metrics, the Is Active filter will be disabled in the query builder with the message: “Is Active filtering is not applicable to Copilot metrics and will not be applied to the overall report.”
- For behavioral metrics only, the Is Active filter will be visible, but users must explicitly select it.
-
Existing queries and Power BI templates:
- Existing recurring queries that contain Copilot or Copilot and behavioral metrics will be disabled and will stop running. Users will be asked to move to a new template.
- A banner will be displayed on existing queries indicating that a new version of the template is available. Users should run reports based on the latest template.
- No automatic updates or modifications will be made to current reports.
-
Other query types:
- No changes are being made to query types where Is Active is not currently seeded by default (for example, Meeting and Network queries).
[Action Required/Recommendations:]
Re-run existing recurring queries using the new templates. Recommended actions: - Review internal guidance and training materials for Advanced Insights analysts.
- Inform report authors that Is Active is no longer automatically applied to new Custom Query – Person queries
- Inform report authors that the Is Active filter will not be applicable for Copilot-only scenarios and scenarios that include both Copilot and behavioral metrics, and will only apply to behavioral metrics when explicitly selected.
- Communicate this change to help desk and analytics support teams to avoid confusion regarding changes in query results after rollout.
- Update internal documentation that describes default query behavior.
Learn more: Filters in advanced analysis queries | Microsoft Learn (will be updated before rollout) [Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| Microsoft Teams: New layout for sharing content in Teams eventsCategory:Microsoft TeamsNummer:MC1419802Status:stayInformed | [What and Why] Microsoft Teams is introducing an updated set of layout options for presenters using the “Manage what attendees see” experience in Teams events. This update includes a new Speaker focused layout, giving organizers the ability to prioritizes presenter videos alongside shared content. This improvement help deliver more engaging and polished events such as town halls and large broadcasts. This message is associated with Microsoft 365 Roadmap ID 564613. [Rollout Schedule] - Targeted Release: Beginning in early August 2026 and expeced to complete by early July 2026
- General Availability
- Worldwide: Beginning in mid-August 2026 and expected to complete by late August 2026
- GCC High: Beginning in early August 2026 and expected to complete by early September 2026
- GCC: Beginning in late August 2026 and expected to complete by mid-September 2026
- DoD: Beginning in early September 2026 and expected to complete by late September 2026
[Impact on Your Organization] Who is affected - Teams event organizers and presenters with a Teams Enterprise license who use production tools
- Users hosting or presenting in Teams events such as town halls
Platforms/Services - Microsoft Teams
- Windows desktop
- Mac desktop
What will happen - Users will see an updated set of layout options when sharing content in Teams events using the “Manage what attendees see” experience.
- Available layouts include:
- Speaker focused (new): Prioritizes presenter video alongside shared content
- Content focused
- Content only
- Existing layout options remain available.
- The feature is enabled by default for eligible users.
- There are no new admin controls for this feature.
[Action Required/Recommendations] No admin action is required before rollout. We recommend that you: - Inform event organizers and presenters about the new layout options.
- Update internal training materials or event playbooks if applicable.
- Consider running a test Teams event to familiarize presenters with the new layouts and attendee experience.
Learn more: Manage what attendees see in Microsoft Teams | Microsoft Support [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. |
| Dynamics 365 Sales – Enable Automatic CRM Record Linking and Suggested Updates for Accounts, Contacts, and LeadsCategory:Dynamics 365 AppsNummer:MC1420564Status:stayInformed | We are announcing the ability to enable Automatic CRM Record Linking and Suggested Updates for Accounts, Contacts, and Leads in Dynamics 365 Sales. This feature will reach general availability on August 7, 2026.
How does this affect me?
This feature enables AI-powered data enrichment that helps you keep related CRM records accurate by automatically surfacing relevant insights from seller conversations. With this enhancement, you get record-level intelligence that:
- Detects accounts, contacts, and leads referenced in emails and meetings, and links them to the relevant opportunity context.
- Suggests field updates such as job title, phone number, industry, or employee count – when new information appears in a conversation.
- Identifies new stakeholders mentioned in meetings or email threads and suggests creating or linking contact and lead records.
- Cites the source interaction for every suggestion so you can verify before applying.
What action do I need to take?
This message is for awareness, and no action is required. |
| Dynamics 365 Contact Center – Privileges and role-based accessCategory:Dynamics 365 AppsNummer:MC1420635Status:stayInformed | We are announcing the ability to use role-based access for agents and customer service representatives using Microsoft Entra ID within Dynamics 365 Contact Center. This feature will reach general availability on July 24, 2026.
How does this affect me?
With this feature, admins can link a Microsoft Entra security group to a Dataverse team of the type Microsoft Entra ID Security Group and assign the required security roles once at the team level, such as Basic User, Customer Service Representative, and Omnichannel Agent. Every member of the linked group inherits those roles automatically, so agents get full functionality with no per-user role assignment, including Queue participation, Presence, and Conversation handling. When an agent belongs to more than one team, they receive the combined privileges of all their teams. Existing persona-based assignments continue to work, so current configurations continue to function without changes.
This feature is not enabled by default. To enable it:- Create a Microsoft Entra security group and add your users as members.
- In the Power Platform admin center, create a Dataverse team, set its team type to Microsoft Entra ID Security Group, and link it to that security group.
- Assign the user security roles to the team rather than to individual users. After setup, adding a user to the Entra group provisions them into the Dataverse team automatically on first sign in, and removing them revokes access. Existing persona-based users remain supported, so you can adopt this model gradually for new users while leaving current users unchanged.
What action do I need to take?
This message is for awareness, and no action is required. |
