19-February-2026 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.
This entire post was automated via Microsoft Flow
have fun reading!
The blogs of this day are:
Office 365 Roadmap Updated: 2026-02-19
Additions : 7
Updates : 12
More Details At: www.roadmapwatch.com
Items from the MessageCenter in Microsoft 365
| (Updated) Microsoft Defender for Office 365: Enhancing the quarantine email preview experienceCategory:Microsoft Defender XDRNummer:MC1166867Status:stayInformed | Updated February 18, 2026: We have updated the content. Thank you for your patience. We’re improving the email preview experience in Microsoft Defender for Office 365 to provide a clearer, more consistent, and secure workflow. These updates are designed to reduce ambiguity, simplify interactions, and reinforce security protections—helping organizations confidently use this feature as part of their protection strategy. When this will happen: General Availability (Worldwide): Rollout will begin in early November 2025 (previously mid-October) and is expected to complete by mid-December 2025 (previously early November). General Availability (GCC, GCCH, and DoD): Rollout will begin in mid-November 2025 (previously late October) and is expected to complete by mid-December 2025 (previously mid-November). How this affects your organization: Who is affected: Quarantine users Microsoft Defender for Office 365 with access to review and preview messages within quarantine. The update is specifically for the preview capability within the quarantine experience. What will happen:
Quarantine users will experience a simplified preview interface with clearer rendering and reduced visual cues for URL interactivity: What you can do to prepare:
Compliance considerations: No compliance considerations identified, review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| (Updated) Introducing simplified admin controls to manage external collaboration in Teams admin centerCategory:Microsoft TeamsNummer:MC1183006Status:stayInformed | Updated February 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction:] We’re introducing a simplified external collaboration (EC) admin experience in Microsoft Teams to help administrators manage external collaboration settings more efficiently. This update introduces two predefined collaboration modes—Open and Controlled—as well as a Custom mode for organizations with unique requirements. The new experience provides a streamlined interface in the Teams admin center (TAC) for configuring external collaboration policies across chats, calls, meetings, Teams, and channels (including shared channels). [When this will happen:] Public Preview: Rolling out mid-November 2025; expected completion by mid-November 2025. General Availability (Worldwide): Rolling out late February 2026 (previously mid-February); expected completion by late February 2026 (previously early February). [How this affects your organization:] Who is affected: Admins managing Microsoft Teams external collaboration settings. What will happen:
Screenshot 1 – A new external collab section and overview page that shows external collab settings at a glance: Screenshot 2: Manage external collab settings using a guided simple UX: [What you can do to prepare:] No action is required at this time. Admins may choose to explore the new interface once available to review and adjust external collaboration settings. For more information, refer to the Teams admin center documentation once the update is live. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| (Updated) Microsoft Edge: Microsoft 365 Copilot will support summarization and contextual groundingCategory:Microsoft 365 suite Microsoft Copilot (Microsoft 365)Nummer:MC1187682Status:stayInformed | Updated February 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction:] Microsoft Edge for Business will soon support summarization and contextual grounding with Microsoft 365 Copilot Chat. This enhancement enables users to ask Copilot questions about multiple open browser tabs, Microsoft 365 documents (such as Word, Excel, PowerPoint), and YouTube videos directly from the Edge side pane. This message is associated with Microsoft 365 Roadmap ID 496364, 499423, and 499424. [When this will happen:] General Availability (Worldwide): We will begin rolling out in mid-February (previously mid-March). [How this affects your organization:] Who is affected: Users signed in to Microsoft Edge for Business with their Entra ID and who have access to Microsoft 365 Copilot. What will happen:
[What you can do to prepare:]
Learn more:
[Compliance considerations:]
| ||||||||||||||||||||||||||||||
| (Updated) Microsoft Purview: Role management updateCategory:Microsoft PurviewNummer:MC1199765Status:stayInformed | Updated February 17, 2026: We have updated the 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:]
[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:
Role Mapping Table:
Example: If you have both Export and Search and Purge roles, you’ll get the Purview Workload Content Administrator role in Entra. [What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified; review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| (Updated) Microsoft Teams: Browser selection for links in Teams MobileCategory:Microsoft TeamsNummer:MC1216263Status:planForChange | Updated February 17, 2026: We have updated the timeline. Thank you for your patience. To improve security and user experience, Teams Mobile users on Android and iOS will soon be able to choose which browser opens non‑Office and PDF links. This update encourages the use of Microsoft Edge—which supports Single Sign-On (SSO), Copilot, and enhanced security—while still allowing users to choose their preferred browser. [When this will happen]General Availability (Worldwide): Rollout will begin in late February 2026 and is expected to complete by late February 2026. General Availability (DoD, GCC, and GCCH): Rollout will begin in late February 2026 and is expected to complete by late February 2026. During rollout, we will monitor user satisfaction (DSAT), Microsoft Edge installation rates, and retention.
[How this affects your organization] Who is affected: All users of Microsoft Teams Mobile on Android and iOS. What will happen:
Admins can manage this feature using PowerShell:
[What you can do to prepare] IT Admins:
Users – To change your preferred browser:
[Compliance considerations] No compliance considerations have been identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| (Updated) Microsoft Teams: Organization evaluation score for apps and agentsCategory:Microsoft TeamsNummer:MC1218713Status:stayInformed | Updated February 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Today, admins must manually review trust and compliance information for Teams apps and agents to determine whether they meet their organization’s security, privacy, and compliance requirements. To make this process more scalable and consistent, Teams will introduce a centralized evaluation experience. Admins will define their organization’s trust requirements once, and the system will generate a score and detailed evaluation report for each app and agent based on those requirements. This will help organizations make faster, more consistent approval decisions. This message is associated with Microsoft 365 Roadmap ID 532720. [When this will happen] General Availability (Worldwide and GCC): We will begin rollout in late February 2026 (previously mid-February) and expect to complete by the end of February 2026. [How this will affect your organization] Who is affected: Admins who manage apps and agents in the Teams admin center. What will happen:
[What you can do to prepare] No action is required. This feature will be available automatically in the Teams admin center. Admins may choose to review their approval workflows once the feature becomes available. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| (Updated) Microsoft Teams: New Drafts quick viewCategory:Microsoft TeamsNummer:MC1223827Status:stayInformed | Updated February 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Teams is introducing a new Drafts quick view feature to help users easily find, edit, and send draft messages. This enhancement improves productivity by making unsent drafts more accessible. This message is associated with Roadmap ID 542789. [When this will happen:]
[How this affects your organization:]
[What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified; review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| (Updated) App names hidden in app bar for a cleaner, more focused experienceCategory:Microsoft TeamsNummer:MC1226220Status:stayInformed | Updated February 17, 2026: We have updated the content. Thank you for your patience. [Introduction] We are updating the Microsoft Teams app bar to create a cleaner and more focused experience. App names will be hidden by default, showing only app icons. Users can still view the app name by hovering over an app icon or navigating to it with keyboard focus, which displays the app name in a tooltip, as it exists today. This update simplifies the app bar by reducing visual noise. Users can choose to show app names anytime in Settings > Appearance. Accessibility reviews have been conducted to verify compliance and ensure screen readers are working properly. [When this will happen] General Availability (Worldwide): We will begin rolling out in mid-March 2026 (previously late February) and expect to complete by early April 2026 (previously early March). [How this affects your organization] Who is affected: All Microsoft Teams users in commercial (non-government) tenants. What will happen:
Screenshot 1 – Before: Screenshot 2 – After:
[What you can do to prepare]
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft 365 apps for Mac suite installer now includes the Microsoft 365 Copilot appCategory:Microsoft 365 suite Microsoft 365 apps Microsoft Copilot (Microsoft 365)Nummer:MC1230456Status:stayInformed | [Introduction] Starting in mid‑February 2026, the Microsoft 365 apps for Mac suite installer will include a shim for the Microsoft 365 Copilot app. This change helps organizations more easily deploy the Microsoft 365 Copilot Mac app by enabling users to download the full application directly from the shim. The Microsoft 365 Copilot Mac app brings AI assistance to macOS, helping users search, analyze, and create from a single, secure desktop experience.
[When this will happen]
[How this affects your organization] Who is affected: Organizations that deploy Microsoft 365 apps for Mac using the suite installation package. What will happen:
[What you can do to prepare] If your organization deploys Microsoft 365 apps for Mac using the suite installer package:
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| March 2026 Secure Score category updateCategory:Microsoft Defender XDRNummer:MC1230458Status:stayInformed | As part of Microsoft’s ongoing efforts to increase accuracy in Secure Score, security recommendation categories will be updated in March 2026. As a result, identity and app Secure Scores may be impacted.
| ||||||||||||||||||||||||||||||
| Updates available for Microsoft 365 Apps for Current ChannelCategory:Microsoft 365 appsNummer:MC1234254Status:stayInformed | We've released updates to the following update channel for Microsoft 365 Apps:
[When this will happen:] We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting February 17th, 2026 (PST). [How this will affect your organization:] If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required. If you manage updates directly you can now download this latest update and begin deployment. [What you need to do to prepare:] To get more details about this update view the following release notes: | ||||||||||||||||||||||||||||||
| Retirement of “Suspected identity theft (pass-the-ticket)” classic alertCategory:Microsoft Defender XDRNummer:MC1234542Status:planForChange | [Introduction] To streamline our alert catalog and focus investment on our unified Microsoft Defender XDR detection capabilities, we’re retiring the “Suspected identity theft (pass‑the‑ticket)” classic alert (External ID: 2018). This retirement aligns with our move toward consolidated XDR alerting and improved detection fidelity. We recommend using the “Pass‑the‑Ticket (PtT) attack” alert (Detector ID: xdr_PassTheTicketAttack), where ongoing development and enhancements will continue. [When this will happen] We’ll retire the classic alert between March 18, 2026 and March 22, 2026. [How this affects your organization] Who is affected:
What will happen:
[What you can do to prepare] No admin action is required for this change, but we recommend the following to ensure continuity in your security workflows:
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Context preservation in Microsoft TeamsCategory:Microsoft TeamsNummer:MC1234548Status:stayInformed | Introduction We’re introducing context preservation behavior in Microsoft Teams that restores recent conversation and view state when users return after a brief period. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It’s associated with Roadmap ID 557184. When this will happen: General Availability (Worldwide): Rollout begins mid-March 2026 and is expected to complete by late March 2026 How this affects your organization: Who is affected:
What will happen:
What you can do to prepare: No action is required Compliance considerations: No compliance considerations identified, review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft SharePoint: Use SharePoint quick steps to automate common tasks and workflows with new column typeCategory:SharePoint OnlineNummer:MC1234549Status:stayInformed | [Introduction] We’re sharing an update to the previously announced Quick steps experience in Microsoft SharePoint. With this update, Quick steps are now available as a column type in SharePoint lists and libraries, expanding how users can trigger common actions directly from their data. This enhancement builds on existing Quick steps capabilities and brings inline automation—such as email, Teams chat, approvals, flows, and column updates—directly into list and library views using a simple sentence‑builder experience similar to SharePoint rules. [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
Learn more: Create a quick step for your list or library | Microsoft Support [What you can do to prepare:]
[Compliance considerations:]
| ||||||||||||||||||||||||||||||
| Simplified Teams app bar to create a cleaner and more focused experienceCategory:Microsoft TeamsNummer:MC1234559Status:planForChange | [Introduction] We’re simplifying the Microsoft Teams app bar to create a cleaner, more focused workspace and help users spend less time navigating and more time collaborating. This update reduces visual clutter and gives users more control over how much screen space the app bar uses. Screenshot: The new Teams app bar
This message is associated with Roadmap ID 557169. [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:] No admin action is required.
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft Teams: Retirement of the Microsoft Teams app from the Amazon AppstoreCategory:Microsoft TeamsNummer:MC1234560Status:planForChange | [Introduction] Microsoft will retire the Microsoft Teams app from the Amazon Appstore to streamline our distribution channels and ensure that customers use the most secure, fully supported Teams experiences. After retirement, we will continue to invest in the Teams Web app and the Teams Android app available through the Google Play Store on supported devices. [When this will happen] The Microsoft Teams app will be retired from the Amazon Appstore in mid-March 2026. [How this affects your organization] Who is affected Organizations with users who install or update Microsoft Teams through the Amazon Appstore. What will happen
[What you can do to prepare] No admin action is required for the retirement to occur. To prepare your organization:
If your organization maintains device-specific deployment instructions, update them accordingly. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft Teams on Windows: Annotate content while sharing a single windowCategory:Microsoft TeamsNummer:MC1234561Status:stayInformed | [Introduction] We’re introducing Annotations on Single Window Sharing for Windows in Microsoft Teams meetings, based on customer feedback requesting more focused and privacy‑preserving collaboration. Presenters can now annotate directly on a shared application window without sharing their entire desktop. This message is associated with Roadmap ID 555239. [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:]
Additional information:
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft Clipchamp added to Office 365 E3 and E5 subscriptionsCategory:Microsoft 365 suite Microsoft Clipchamp Nummer:MC1234562Status:planForChange | [Introduction] Microsoft Clipchamp is being added as a service plan to additional Office 365 E3 and E5 subscriptions. This update expands access to video creation capabilities already included with Microsoft 365, helping users create and edit videos more easily using built-in tools such as templates, captions, and AI-assisted features. This change reflects ongoing investments to improve content creation experiences within Microsoft 365. [When this will happen] General Availability (Worldwide): Rollout begins mid-March 2026 and completes by late April 2026. [How this affects your organization] Who is affected:
What will happen:
[What you can do to prepare]
[Compliance considerations] No compliance considerations identified, review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft Dataverse – Guided Table Selection for First‑Time Dataverse SyncCategory:Microsoft DataverseNummer:MC1234563Status:stayInformed | We are announcing guided table selection for first-time Dataverse sync in Microsoft Dataverse. This feature will reach general availability on March 15, 2026. How does this affect me? This feature enables table selection during the initial sync of Dataverse data to Microsoft Fabric, allowing you to choose which Dataverse tables are synced before any data movement begins. This provides a more intuitive initial setup, lower storage and compute costs, and a more predictable analytics experience. What action do I need to take? This message is for awareness and no action is required. | ||||||||||||||||||||||||||||||
| Outlook: retiring “Contact Masking” (hide suggested recipients) – March 31, 2026Category:Microsoft 365 suiteNummer:MC1234566Status:planForChange | [What’s changing]
In Outlook, users can hide a suggested recipient while addressing an email. For example, selecting the X next to a name in the To/Cc/Bcc suggestions list. This behaviour is commonly referred to as “Contact Masking”.
We are retiring this feature for users. This does not impact admin controls for contacts. [When this will happen]
Contact masking will reach end of support on March 31, 2026. [How this affects your organization] Who is affected
[Why we’re making this change] This feature has been a recurring source of customer confusion and escalations, because contacts can be accidentally hidden for one user but not others. While the impact is felt across Microsoft 365 experiences (not just Outlook). It also isn’t managed as a contact entity setting, which creates transparency and compliance challenges. [What will change in user experience]
[Is Admin Action Required?] No action is required for this retirement. You may choose to:
Learn more about the retiring feature: (RETIRING March 31, 2006) Manage suggested recipients in the To, Cc, and Bcc fields in Outlook | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization guidance to users on user level features. | ||||||||||||||||||||||||||||||
| Microsoft Rewards: Retirement of Azure AD Account LinkingCategory:Microsoft EntraNummer:MC1234567Status:planForChange | [Introduction] [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:]
[Compliance considerations:]
| ||||||||||||||||||||||||||||||
| Search feedback experience update: Legacy SearchCategory:Microsoft 365 suiteNummer:MC1234570Status:planForChange | [Introduction] We have retired the legacy Search & Intelligence Feedback portal and consolidated all Microsoft Search feedback into the standard Product feedback experience in Microsoft 365. This change simplifies how feedback is collected, aligns Search feedback with other Microsoft 365 products, and improves policy compliance across services. [When this will happen] We apologize that this retirement was not communicated in advance, and we are continuing to improve our processes to provide more proactive communication. This retirement has already been completed and is now fully in effect. [How this affects your organization] Who is affected
What will happen
[What you can do to prepare] You may want to:
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft Purview | Data Loss Prevention – Adaptive scopes for DLP for SharePointCategory:Microsoft PurviewNummer:MC1234571Status:stayInformed | [Introduction] Adaptive scopes for SharePoint DLP policies in Microsoft Purview enable you to target SharePoint sites based on site attributes instead of manually maintaining static site lists. As sites are created or updated, adaptive scopes automatically adjust membership, ensuring that DLP policies remain aligned to your environment without ongoing manual updates. This message is associated with Microsoft 365 Roadmap ID 549288. [When this will happen]
[How this will affect your organization] Who is affected: Admins who manage Data Loss Prevention (DLP) policies for SharePoint in Microsoft Purview. What will happen: With adaptive scopes for SharePoint, your organization will –
Additional notes:
[What you can do to prepare] To prepare for this update, you can:
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| AMR‑WB codec support added to Teams Direct Routing SIP interfaceCategory:Microsoft TeamsNummer:MC1234572Status:stayInformed | [Introduction] Microsoft will add support for the Adaptive Multi‑Rate Wideband (AMR‑WB) codec to improve audio quality for calls placed through Teams Direct Routing. This enhancement will introduce wideband audio capabilities when supported by your Session Border Controller (SBC) and will apply to non‑media‑bypass scenarios where the Session Initiation Protocol (SIP) interface negotiates codecs with the Teams service. [When this will happen]
[How this affects your organization] Who is affected:
What will happen:
[What you can do to prepare] Most organizations will not need to take action. Recommended steps for SBC administrators:
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Microsoft Teams: New controls for quick views in the chat listCategory:Microsoft TeamsNummer:MC1234574Status:stayInformed | [Introduction] We will introduce new controls that allow users to customize how quick views appear at the top of their chat and channels lists in Microsoft Teams. This update aligns with customer feedback requesting a cleaner and more focused experience. These controls will help users see only the quick views that are relevant to them and manage when those views appear. This message is associated with Microsoft 365 Roadmap ID 555856. [When this will happen]
[How this affects your organization] Who is affected: All Microsoft Teams users in commercial Microsoft 365 tenants. What will happen:
[What you can do to prepare] No admin action will be required to enable this feature. You may want to:
[Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||||||||||||||||||||||
| Follow‑up on Required Custom Domain Configuration for Teams Event Email TemplatesCategory:Microsoft TeamsNummer:MC1234575Status:stayInformed | [Introduction] To ensure reliable delivery of Teams Events email notifications—and to protect organizations using custom HTML templates—we’re enforcing a requirement that all templates reference a verified custom domain in your Microsoft 365 tenant. This improves deliverability, reduces spoofing risk, and aligns with modern email authentication standards. As previously communicated in MC1176301 (October 2025), templates not configured with a verified domain may no longer function as expected after enforcement. [When this will happen:] [How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:]
Learn more: [Compliance considerations:] | ||||||||||||||||||||||||||||||
| Dynamics 365 Customer Insights – Drive confident engagement with enhanced consent‑based segmentationCategory:Dynamics 365 AppsNummer:MC1234577Status:stayInformed | We are announcing improvements to enhanced consent‑based segmentation in Dynamics 365 Customer Insights – Journeys. This feature will reach general availability on March 20, 2026. How does this affect me? This feature improves consent-based segments to provide clear and consistent consent evaluation, allowing you to trust that the audience you build truly reflects the consent choices your customers have made. Key improvements introduced by this feature include:
This message is for awareness and no action is required. | ||||||||||||||||||||||||||||||
| Dynamics 365 Customer Service – Quality Evaluation Agent for Bulk Case EvaluationCategory:Dynamics 365 AppsNummer:MC1234588Status:stayInformed | We are announcing the ability to use Quality Evaluation Agent (QEA) for Bulk Case Evaluation in Dynamics 365 Customer Service. This feature will reach general availability on March 20, 2026. How does this affect me? This feature enables supervisors to automate continuous quality assessments across their organization at scale. By scheduling evaluations on targeted sets of cases, teams maintain consistent oversight of quality trends, detect issues early, and measure performance without manual effort or disruption. QEA Bulk Case Evaluation allows supervisors to create evaluation plans directly on the case entity record and run them on a defined schedule. Each plan targets a subset of cases based on supervisor‑defined conditions, ensuring evaluations focus on the most relevant interactions. Supervisors can edit evaluation plans at any time, with updates applied to future runs while past executions remain preserved for reference. Every execution is logged in a run history view, giving full visibility into when evaluations ran, which cases were included, and how quality outcomes evolved over time. Bulk evaluations are integrated with QEA evaluation criteria versioning and always reference the published criteria version in effect at runtime. This ensures consistent and traceable quality measurements. What action do I need to take? This message is for awareness, and no action is required. | ||||||||||||||||||||||||||||||
| (Updated) Microsoft Teams admin center: App centric management for app installation and changes to app setup policiesCategory:Microsoft TeamsNummer:MC795355Status:planForChange | Updated February 17, 2026: We have updated the timeline. Thank you for your patience. Coming soon for Microsoft Teams: App centric management for admin app installation introduces new admin settings to control who in the tenant has specific Teams apps preinstalled. Similar to app centric management for app availability, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023), admins will be able to install apps for users, groups, or everyone in the organization. After rollout, app-centric management will let admins install apps individually. Existing Installed apps in app setup policies will remain intact; however, no new additions will be permitted, and only deletions will be allowed. Instead, you can install Teams apps for selected users, groups, or all users directly from the respective app. Other settings in app setup policies, including Pinned apps, will remain unchanged. This message is associated with Microsoft 365 Roadmap ID 394274 and 500637. [When this will happen:] App centric management will roll out in following General Availability phases.
[How this will affect your organization:] Before the rollout: If you install an app to a user, the user cannot actually use an admin preinstalled app if you did not take the additional step to allow the user to use it. After the rollout, if you install an app through app centric management, the user will immediately be able to use the app. After the rollout, you can install any number of Teams apps for selected sets of users, groups, or all users in the organization from the respective apps. Learn more: Preinstall Teams apps for your org users – Microsoft Teams | Microsoft Learn [What you need to do to prepare:] No action needed for Phase 1 tenants. We will update this message with more information before the rollouts for Phases 2 tenants. You may want to update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation. | ||||||||||||||||||||||||||||||
| (Update)Microsoft 365 and Microsoft Teams: Unified management of Teams apps in Teams, Outlook, and the Microsoft 365 appCategory:Microsoft Teams Microsoft 365 appsNummer:MC796790Status:planForChange | Updated February 17, 2026: We have updated the timeline and content below. Thank you for your patience. What it is Microsoft is rolling out a new feature to streamline how app and agent availability is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you’ll be able to unify availability policies for apps and agents across both portals, making app management more consistent and efficient. This message is associated with Microsoft 365 Roadmap ID 393931, 485712 and 503105. When this will happen: We will begin rolling out this feature late September 2025 and expect to complete by end of June 2026 (previously mid-November 2025). 1. Phase 1 – Default Tenant Unification We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931. 2. Phase 2 – Modified Tenants Unification This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers.
Note: In this phase, no changes will be applied to org-wide settings or app-level settings without administrator action. 3. Phase 3 – Automatic Unification Tenants that haven’t transitioned as part of Phase 1 & Phase 2, will be automatically moved to unified app agent management. We will update this post with a timeline and more details later. How this will affect your organization Before this rollout, managing Teams apps that work in Outlook and the Microsoft 365 app was fragmented between the Integrated apps page in the Microsoft 365 admin center for Outlook and the Microsoft 365 app, and the Teams admin center for Teams. This sometimes resulted in different settings for the same app in the two admin centers. With Unified agent app management, you will be able to manage apps on the Integrated apps page in the Microsoft 365 admin center or in the Teams admin center, and any changes made in either admin center will synchronize. What you can expect:
What you need to do to prepare To ensure a smooth transition, review your tenant-level and individual agent/app settings (app allow/block & user availability) in both the Microsoft 365 Admin Center and the Teams Admin Center. If different departments within your organization manage these settings, we suggest coordinating efforts to complete the review collaboratively. This update will be rolled out automatically by the stated date, and no immediate action is required. However, it’s a good time to update any internal documentation related to agent and app management policies.
|
