Microsoft is preparing to make Copilot a far more visible part of Outlook classic for Windows, with a new dedicated entry point scheduled to begin rolling out in August. The planned interface change is modest on paper, but it carries a larger message: Outlook classic is no longer simply the feature-rich legacy client that many businesses continue to rely on. It is becoming another central surface for Microsoft’s AI strategy.
The change is tracked under Microsoft 365 Roadmap ID 567007 and is intended to bring Outlook classic closer to the Copilot experience already seen in Word, Excel, PowerPoint, Outlook on the web, and the new Outlook for Windows. Microsoft’s aim is to provide a consistent place to invoke its AI assistant, with the service able to understand the current work context and draw on the wider Microsoft 365 environment where an organization’s configuration and licensing permit it.
For organizations still anchored to the classic desktop client, this is significant. Outlook classic remains crucial in many Windows environments because of its mature feature set, deep support for enterprise workflows, long-established add-ins, shared mailboxes, delegate scenarios, data files, and advanced mail management. Microsoft is therefore not treating Copilot integration as exclusive to its newer Outlook client. Instead, it is bringing the AI experience directly to the version many business users have chosen not to leave behind.
At the same time, a more prominent Copilot button will sharpen difficult questions around user choice, licensing, governance, reliability, and interface clutter. Microsoft may describe the move as a streamlined entry point, but for users who have already grown weary of increasingly persistent AI controls across Windows and Microsoft 365, it may feel like another step toward making Copilot unavoidable.
The roadmap item describes a new Copilot entry point in classic Outlook designed to make interaction with the service more consistent across Microsoft 365 applications. Microsoft has not publicly detailed the final placement or supplied a complete visual mock-up, so it would be premature to state exactly where the new control will appear in Outlook classic.
The most likely destination is the upper area of the Outlook interface, potentially in or around the Ribbon, where users can access prominent commands without navigating through menus. This would align with the direction Microsoft has taken in other productivity apps, where Copilot is increasingly positioned as a first-class command rather than an optional feature hidden in a contextual menu or task pane.
That matters because placement strongly influences adoption. A command buried in an overflow menu is available when needed. A dedicated button in the primary UI becomes part of the application’s visual hierarchy and gently, but continuously, encourages use.
Microsoft’s stated objective is to make the experience feel coherent across its applications. In theory, that is sensible. Users moving between Outlook, Word, Excel, PowerPoint, and browser-based Microsoft 365 tools should not need to learn a different route to AI features in every app.
The broader objective is clearer still: Copilot is being positioned as a connected layer across Microsoft 365, not a standalone chatbot that users open only when they remember it exists.
Depending on feature availability, tenant configuration, and licensing, Microsoft 365 Copilot in Outlook can support workflows such as:
That is the upside. The challenge is that email is also among the most sensitive information stores in any organization. An AI assistant operating within Outlook must be useful enough to justify the trust, governance, and training required to deploy it responsibly.
Yet Outlook classic remains indispensable in many enterprises.
The classic client has accumulated years of capabilities that matter in practical, unglamorous ways. Advanced Rules, extensive add-in compatibility, specialized mailbox arrangements, established compliance workflows, offline use patterns, complex profile configurations, and support for certain legacy processes all contribute to its staying power.
For many Windows administrators, Outlook classic is not merely the old version. It is the version that supports the organization’s actual operational requirements.
Even when the new client improves, organizations may have valid reasons to remain on classic Outlook for the near term. That makes it commercially important for Microsoft to keep delivering selected modern experiences to the classic client rather than treating it as frozen software.
Copilot is one of those experiences.
The addition of a new Copilot entry point indicates that Microsoft sees classic Outlook as a strategically relevant endpoint for AI adoption. It also helps reduce a potential objection from enterprise customers: that they must abandon a proven desktop workflow merely to access Microsoft’s newest AI tools.
Microsoft can now argue that organizations do not necessarily need to choose between Outlook classic functionality and Microsoft 365 Copilot integration. At least for supported scenarios, they can have both.
That distinction will matter to IT teams. The words “Copilot in Outlook” are increasingly too broad to communicate exactly what users can access.
Administrators will need to distinguish between:
That parallel matters because it illustrates a broader pattern. Microsoft is not only adding AI features alongside conventional productivity tools; it is increasingly consolidating certain insights and assistance features under the Copilot brand.
For users, the result could be more capable meeting preparation. Copilot-based experiences can potentially bring together email discussions, calendar details, documents, previous communications, and organizational context in a single response.
For organizations, though, there is a more complicated implication. A useful workflow that once existed as a familiar built-in feature can become intertwined with Copilot eligibility, data access requirements, and potentially a more complex licensing model.
But there are meaningful risks when AI becomes the preferred gateway to information:
Microsoft will need to demonstrate that Copilot is an improvement in workflow quality, not simply a new branded layer placed between users and their existing data.
That approach is visible throughout Windows and Microsoft 365. Copilot has appeared in application headers, side panes, contextual commands, task-oriented prompts, and dedicated buttons. The goal is clear: reduce the friction between a user’s task and the AI service Microsoft wants them to use.
Microsoft has described its direction as an AI-forward design system intended to feel more intentional and humane. The language is notable because AI interface design is becoming a distinct discipline. It is no longer enough to bolt a chat window onto a product and call it intelligent.
A good AI interface must answer several practical questions:
The downside is equally obvious. Floating or unusually prominent buttons can obstruct content, disrupt established habits, and create the perception that an application is prioritizing AI promotion over the user’s immediate task.
Microsoft has already seen that interface changes involving Copilot can generate strong feedback. Users who spend all day in Word, Excel, PowerPoint, or Outlook often build muscle memory around long-standing layouts. Even a small shift in the location of a command can be frustrating when repeated hundreds of times a week.
That means the new Outlook classic button should be judged less on whether it exists and more on how it behaves.
A successful implementation would be:
Microsoft 365 Copilot deployment depends on several factors, including the user’s assigned licenses, identity setup, mailbox location, connected experiences settings, network configuration, and the organization’s own controls. Certain mailbox-grounded scenarios require the user’s primary mailbox to be hosted in Exchange Online.
That complexity may be invisible to an end user who simply clicks a new Copilot button and expects it to work.
The consequences are predictable:
For many organizations, the best Copilot deployment is not a universal switch. It is a phased rollout based on use cases, data readiness, user training, and measurable business value.
That is important, but it is not the end of the governance conversation.
AI can make it easier to discover, summarize, connect, and repurpose information that was previously difficult to find. This can reveal oversharing problems that have existed for years in SharePoint, OneDrive, Teams, and Exchange but were less visible because the information was harder to locate.
When Copilot uses mailbox grounding to help summarize or answer questions, the quality of results depends on the quality of access controls and data hygiene underneath it.
Organizations deploying Copilot in Outlook classic should review:
A dedicated Copilot button in Outlook classic may increase usage simply because the service is easier to invoke. That makes it more important for organizations to establish policies before widespread deployment rather than after employees have integrated AI into daily email workflows.
The first is workflow continuity. Users who prefer the established desktop client can access a more modern Copilot experience without being pushed into a different Outlook application solely for AI features.
The second is consistency. If the entry point works similarly across Outlook, Word, Excel, and PowerPoint, it reduces the cognitive load of moving between apps. Users can develop an understanding of when and how to call on Copilot without relearning the interface.
The third is contextual utility. Email work often involves repetitive, time-consuming tasks: reading long threads, turning rough notes into polished messages, identifying commitments, and preparing for meetings. These are precisely the areas where AI assistance can save time when the output is accurate and reviewed appropriately.
The fourth is centralized management. Microsoft’s wider Copilot governance tools give enterprise administrators a clearer framework for overseeing AI than a patchwork of unsanctioned third-party browser extensions or consumer chatbots.
For IT departments, the safer path is generally not to pretend generative AI does not exist. It is to offer approved, controlled tools where employees already work, while applying identity, compliance, and data protection safeguards.
Rollouts may occur gradually across release channels, geographies, cloud environments, and tenant configurations. Features can also change in scope before they reach general availability. A roadmap entry is useful for planning, but it is not a final product contract.
IT administrators should watch for the feature in Microsoft 365 message center communications, release notes, and their selected update channels. They should also test the experience with representative users before assuming it will behave uniformly across all mailbox types, license tiers, devices, and organizational policies.
By placing Copilot more prominently in the classic application, Microsoft is extending its AI platform to users who may otherwise remain outside the company’s preferred modern interface. That is a pragmatic decision, and potentially a useful one.
The quality of the execution will determine whether users see the change as progress. If Copilot becomes a fast, contextual assistant that helps people handle email overload, prepare for meetings, and create better communications, the dedicated entry point could earn its place in the Outlook Ribbon.
If it becomes an intrusive promotional control, an inconsistent licensing prompt, or a replacement for straightforward features that did not need AI in the first place, it will reinforce skepticism about Microsoft’s increasingly aggressive Copilot integration.
For now, the August rollout should be viewed as more than a button placement update. It is another indication that Microsoft 365 Copilot is becoming part of the default interface philosophy of Windows productivity software—including the classic Outlook client that many organizations still depend on every day.
The change is tracked under Microsoft 365 Roadmap ID 567007 and is intended to bring Outlook classic closer to the Copilot experience already seen in Word, Excel, PowerPoint, Outlook on the web, and the new Outlook for Windows. Microsoft’s aim is to provide a consistent place to invoke its AI assistant, with the service able to understand the current work context and draw on the wider Microsoft 365 environment where an organization’s configuration and licensing permit it.
For organizations still anchored to the classic desktop client, this is significant. Outlook classic remains crucial in many Windows environments because of its mature feature set, deep support for enterprise workflows, long-established add-ins, shared mailboxes, delegate scenarios, data files, and advanced mail management. Microsoft is therefore not treating Copilot integration as exclusive to its newer Outlook client. Instead, it is bringing the AI experience directly to the version many business users have chosen not to leave behind.
At the same time, a more prominent Copilot button will sharpen difficult questions around user choice, licensing, governance, reliability, and interface clutter. Microsoft may describe the move as a streamlined entry point, but for users who have already grown weary of increasingly persistent AI controls across Windows and Microsoft 365, it may feel like another step toward making Copilot unavoidable.
A New Copilot Entry Point for Outlook Classic
The roadmap item describes a new Copilot entry point in classic Outlook designed to make interaction with the service more consistent across Microsoft 365 applications. Microsoft has not publicly detailed the final placement or supplied a complete visual mock-up, so it would be premature to state exactly where the new control will appear in Outlook classic.The most likely destination is the upper area of the Outlook interface, potentially in or around the Ribbon, where users can access prominent commands without navigating through menus. This would align with the direction Microsoft has taken in other productivity apps, where Copilot is increasingly positioned as a first-class command rather than an optional feature hidden in a contextual menu or task pane.
That matters because placement strongly influences adoption. A command buried in an overflow menu is available when needed. A dedicated button in the primary UI becomes part of the application’s visual hierarchy and gently, but continuously, encourages use.
Microsoft’s stated objective is to make the experience feel coherent across its applications. In theory, that is sensible. Users moving between Outlook, Word, Excel, PowerPoint, and browser-based Microsoft 365 tools should not need to learn a different route to AI features in every app.
The broader objective is clearer still: Copilot is being positioned as a connected layer across Microsoft 365, not a standalone chatbot that users open only when they remember it exists.
What Contextual Copilot Could Mean in Email
In Outlook, context is unusually valuable. An email client is not just a place to type messages; it is a hub for conversations, calendars, contact relationships, meeting details, files, and task commitments. That gives Copilot substantial potential to help with everyday work when it can accurately identify what the user is viewing.Depending on feature availability, tenant configuration, and licensing, Microsoft 365 Copilot in Outlook can support workflows such as:
- Summarizing a lengthy email thread
- Drafting or rewriting messages
- Adjusting the tone or length of an email
- Identifying action items from a conversation
- Preparing users for meetings
- Surfacing relevant calendar and mailbox context
- Helping convert email discussions into meetings or follow-up actions
- Answering questions based on accessible work content
That is the upside. The challenge is that email is also among the most sensitive information stores in any organization. An AI assistant operating within Outlook must be useful enough to justify the trust, governance, and training required to deploy it responsibly.
Why Outlook Classic Still Matters to Microsoft
It would be easy to assume Microsoft’s long-term Outlook strategy is solely about moving customers to the new Outlook for Windows. The company continues to develop the newer client, which is based on a more modern, web-connected architecture and is increasingly linked to Microsoft’s wider service ecosystem.Yet Outlook classic remains indispensable in many enterprises.
The classic client has accumulated years of capabilities that matter in practical, unglamorous ways. Advanced Rules, extensive add-in compatibility, specialized mailbox arrangements, established compliance workflows, offline use patterns, complex profile configurations, and support for certain legacy processes all contribute to its staying power.
For many Windows administrators, Outlook classic is not merely the old version. It is the version that supports the organization’s actual operational requirements.
The Reality of Enterprise Migration
Moving thousands of workers from Outlook classic to the new Outlook is not a simple software update. It can require testing, training, policy adjustments, add-in verification, data migration planning, and a careful assessment of missing or changed features.Even when the new client improves, organizations may have valid reasons to remain on classic Outlook for the near term. That makes it commercially important for Microsoft to keep delivering selected modern experiences to the classic client rather than treating it as frozen software.
Copilot is one of those experiences.
The addition of a new Copilot entry point indicates that Microsoft sees classic Outlook as a strategically relevant endpoint for AI adoption. It also helps reduce a potential objection from enterprise customers: that they must abandon a proven desktop workflow merely to access Microsoft’s newest AI tools.
Microsoft can now argue that organizations do not necessarily need to choose between Outlook classic functionality and Microsoft 365 Copilot integration. At least for supported scenarios, they can have both.
Feature Parity Is Not the Same as Experience Parity
However, sharing a Copilot button does not guarantee equivalent functionality across every Outlook version or Microsoft 365 plan. Outlook on the web, new Outlook, classic Outlook, the Microsoft 365 Copilot app, and Teams can each expose different capabilities at different times.That distinction will matter to IT teams. The words “Copilot in Outlook” are increasingly too broad to communicate exactly what users can access.
Administrators will need to distinguish between:
- Copilot Chat and paid Microsoft 365 Copilot experiences
- Consumer and commercial accounts
- Cloud-hosted and hybrid mailbox deployments
- New Outlook and classic Outlook feature availability
- Tenant-level controls and individual licensing
- Features enabled by default versus experiences that require explicit configuration
- Current Channel, preview, targeted release, and broad rollout timelines
The Meeting Insights Change Adds Important Context
The new Outlook classic entry point does not stand alone. It arrives as Microsoft is also moving away from Meeting Insights in Outlook classic and directing customers toward a Copilot-based alternative for meeting preparation.That parallel matters because it illustrates a broader pattern. Microsoft is not only adding AI features alongside conventional productivity tools; it is increasingly consolidating certain insights and assistance features under the Copilot brand.
For users, the result could be more capable meeting preparation. Copilot-based experiences can potentially bring together email discussions, calendar details, documents, previous communications, and organizational context in a single response.
For organizations, though, there is a more complicated implication. A useful workflow that once existed as a familiar built-in feature can become intertwined with Copilot eligibility, data access requirements, and potentially a more complex licensing model.
The Risk of Feature Replacement
Replacing or retiring traditional features in favor of AI alternatives is not automatically a negative development. If the replacement is faster, more accurate, more accessible, and broadly available, it may represent genuine progress.But there are meaningful risks when AI becomes the preferred gateway to information:
- A deterministic interface can become a probabilistic one.
- A simple data view can be replaced by an AI-generated summary.
- A feature that worked predictably may depend on licensing, connectivity, or service availability.
- Users may need to verify AI output instead of trusting a clearly presented set of facts.
- Organizations may find that important convenience features are now tied more closely to premium AI access.
Microsoft will need to demonstrate that Copilot is an improvement in workflow quality, not simply a new branded layer placed between users and their existing data.
Microsoft’s AI-Forward Interface Strategy
The Outlook classic update also fits a wider shift in Microsoft’s product design. Copilot is moving from being an occasional assistant to becoming an increasingly obvious presence in the interfaces people use every day.That approach is visible throughout Windows and Microsoft 365. Copilot has appeared in application headers, side panes, contextual commands, task-oriented prompts, and dedicated buttons. The goal is clear: reduce the friction between a user’s task and the AI service Microsoft wants them to use.
Microsoft has described its direction as an AI-forward design system intended to feel more intentional and humane. The language is notable because AI interface design is becoming a distinct discipline. It is no longer enough to bolt a chat window onto a product and call it intelligent.
A good AI interface must answer several practical questions:
- What does the AI understand right now?
- Which files, messages, calendar items, or work data can it access?
- What will happen if the user approves an AI-generated action?
- How can users verify the result?
- How can they dismiss, disable, or ignore the feature when it is not useful?
Lessons From Dynamic Action Buttons
Microsoft has experimented with more assertive Copilot controls in Office apps, including interface concepts that position AI actions directly above a user’s work. The value proposition is obvious: the assistant is available at the moment of need, without forcing users to leave the content they are editing.The downside is equally obvious. Floating or unusually prominent buttons can obstruct content, disrupt established habits, and create the perception that an application is prioritizing AI promotion over the user’s immediate task.
Microsoft has already seen that interface changes involving Copilot can generate strong feedback. Users who spend all day in Word, Excel, PowerPoint, or Outlook often build muscle memory around long-standing layouts. Even a small shift in the location of a command can be frustrating when repeated hundreds of times a week.
That means the new Outlook classic button should be judged less on whether it exists and more on how it behaves.
A successful implementation would be:
- Easy to find without being visually dominant
- Predictable across Outlook views
- Accessible by keyboard and assistive technologies
- Clear about the work context it is using
- Non-disruptive when users do not have a Copilot license
- Respectful of customization and enterprise policy
- Easy for organizations to manage and support
Licensing Will Determine Whether the Button Feels Useful
One of the biggest practical considerations is that seeing Copilot in Outlook classic is not the same as receiving every Copilot capability.Microsoft 365 Copilot deployment depends on several factors, including the user’s assigned licenses, identity setup, mailbox location, connected experiences settings, network configuration, and the organization’s own controls. Certain mailbox-grounded scenarios require the user’s primary mailbox to be hosted in Exchange Online.
That complexity may be invisible to an end user who simply clicks a new Copilot button and expects it to work.
The “Visible but Unavailable” Problem
A prominent Copilot entry point can become a source of confusion if it opens a limited experience, displays a licensing prompt, or remains unavailable because of tenant configuration. This has been a recurring problem across modern software: product teams make an advanced feature highly visible, while IT departments must explain why it does not work for everyone.The consequences are predictable:
- Help desk calls increase.
- Users assume something is broken.
- Managers question why teams have inconsistent access.
- Administrators must explain subtle differences between subscriptions.
- AI adoption becomes associated with friction instead of productivity.
For many organizations, the best Copilot deployment is not a universal switch. It is a phased rollout based on use cases, data readiness, user training, and measurable business value.
Governance and Privacy Cannot Be an Afterthought
Microsoft 365 Copilot is designed to operate within the permissions model already applied to an organization’s Microsoft 365 data. In simple terms, Copilot should not grant users access to content they could not otherwise access.That is important, but it is not the end of the governance conversation.
AI can make it easier to discover, summarize, connect, and repurpose information that was previously difficult to find. This can reveal oversharing problems that have existed for years in SharePoint, OneDrive, Teams, and Exchange but were less visible because the information was harder to locate.
Outlook Raises the Stakes
Email contains sensitive material by default. A typical enterprise mailbox can include customer details, internal financial discussions, personnel topics, security notifications, strategy documents, meeting agendas, and informal conversations that were never intended to be broadly surfaced.When Copilot uses mailbox grounding to help summarize or answer questions, the quality of results depends on the quality of access controls and data hygiene underneath it.
Organizations deploying Copilot in Outlook classic should review:
- Exchange mailbox permissions and delegation practices
- Shared mailbox access
- Sensitive information types and data loss prevention policies
- Retention rules and eDiscovery requirements
- Microsoft Purview labeling and classification
- SharePoint and OneDrive oversharing risks
- Policies for web grounding and external data access
- Prompt and response auditing capabilities
- User education around verifying generated content
A dedicated Copilot button in Outlook classic may increase usage simply because the service is easier to invoke. That makes it more important for organizations to establish policies before widespread deployment rather than after employees have integrated AI into daily email workflows.
Benefits for Windows Users and IT Teams
Despite the concerns, there are real reasons to welcome the Outlook classic update.The first is workflow continuity. Users who prefer the established desktop client can access a more modern Copilot experience without being pushed into a different Outlook application solely for AI features.
The second is consistency. If the entry point works similarly across Outlook, Word, Excel, and PowerPoint, it reduces the cognitive load of moving between apps. Users can develop an understanding of when and how to call on Copilot without relearning the interface.
The third is contextual utility. Email work often involves repetitive, time-consuming tasks: reading long threads, turning rough notes into polished messages, identifying commitments, and preparing for meetings. These are precisely the areas where AI assistance can save time when the output is accurate and reviewed appropriately.
The fourth is centralized management. Microsoft’s wider Copilot governance tools give enterprise administrators a clearer framework for overseeing AI than a patchwork of unsanctioned third-party browser extensions or consumer chatbots.
For IT departments, the safer path is generally not to pretend generative AI does not exist. It is to offer approved, controlled tools where employees already work, while applying identity, compliance, and data protection safeguards.
What to Expect From the August Rollout
Microsoft currently lists August as the rollout starting point for the new Copilot entry point in Outlook classic. As with every Microsoft 365 roadmap item, that date should be treated as a target rather than a guarantee.Rollouts may occur gradually across release channels, geographies, cloud environments, and tenant configurations. Features can also change in scope before they reach general availability. A roadmap entry is useful for planning, but it is not a final product contract.
IT administrators should watch for the feature in Microsoft 365 message center communications, release notes, and their selected update channels. They should also test the experience with representative users before assuming it will behave uniformly across all mailbox types, license tiers, devices, and organizational policies.
A Practical Readiness Checklist
Organizations that expect the new Outlook classic Copilot button to arrive soon should prepare in advance:- Confirm licensing for the users expected to access Copilot capabilities.
- Verify mailbox hosting and ensure supported users have Exchange Online primary mailboxes where required.
- Review privacy settings and connected experiences policies in Microsoft 365 Apps.
- Audit data permissions, particularly shared mailboxes, delegated access, SharePoint sites, and OneDrive libraries.
- Define acceptable-use guidance for drafting, summarization, external sharing, and fact checking.
- Prepare support documentation explaining what Copilot can and cannot do in Outlook classic.
- Pilot the feature with departments that have clear, repeatable email and meeting workflows.
- Collect user feedback on discoverability, performance, accuracy, and interface disruption.
Outlook Classic Is Becoming an AI Endpoint, Not a Holdover
The upcoming Copilot entry point is a meaningful signal about Microsoft’s view of Outlook classic. The company is still developing newer Outlook experiences and clearly wants its modern client to grow, but it also recognizes that classic Outlook continues to matter in the Windows enterprise landscape.By placing Copilot more prominently in the classic application, Microsoft is extending its AI platform to users who may otherwise remain outside the company’s preferred modern interface. That is a pragmatic decision, and potentially a useful one.
The quality of the execution will determine whether users see the change as progress. If Copilot becomes a fast, contextual assistant that helps people handle email overload, prepare for meetings, and create better communications, the dedicated entry point could earn its place in the Outlook Ribbon.
If it becomes an intrusive promotional control, an inconsistent licensing prompt, or a replacement for straightforward features that did not need AI in the first place, it will reinforce skepticism about Microsoft’s increasingly aggressive Copilot integration.
For now, the August rollout should be viewed as more than a button placement update. It is another indication that Microsoft 365 Copilot is becoming part of the default interface philosophy of Windows productivity software—including the classic Outlook client that many organizations still depend on every day.
References
- Primary source: Neowin
Published: 2026-07-23T11:30:01+00:00
Microsoft wants to make Copilot an integral component of Outlook classic | Neowin
Microsoft is making AI even harder to ignore in its classic email client, with another interface change arriving sooner than many hoped.
www.neowin.net
- Related coverage: windowscentral.com
Microsoft is moving another Outlook feature behind a Copilot paywall | Windows Central
Meeting Insight is being retired in favor of a paid Copilot experience, continuing a frustrating trend for Microsoft 365 users.www.windowscentral.com - Official source: learn.microsoft.com
App and network requirements for Microsoft 365 Copilot admins | Microsoft Learn
Enterprise and company IT admins can learn about the Microsoft 365 app and network requirements for Microsoft 365 Copilot. Admins must configure features in popular apps, like OneDrive, Teams, Loop, and Whiteboard that allow Copilot. Allow the network and endpoint URLs for Microsoft 365 Copilot...learn.microsoft.com - Official source: support.microsoft.com
Feature comparison between new Outlook and classic Outlook | Microsoft Support
Feature comparison between new Outlook and classic Outlooksupport.microsoft.com - Official source: microsoft.com
Microsoft 365 Roadmap | Microsoft 365
The Microsoft 365 Roadmap lists updates that are currently planned for applicable subscribers. Check here for more information on the status of new features and updates.www.microsoft.com
- Related coverage: techradar.com
Microsoft's planned new AI trick for Edge will 'automatically open the Copilot side pane' with Outlook email links — and I can feel the hate already | TechRadar
New feature is on the roadmap for May 2026www.techradar.com