Microsoft confirmed on July 8, 2026, that Teams on Android and iOS will soon open SharePoint page and news links directly inside the Teams app, rather than shunting users out to a mobile browser. The change, filed under Microsoft 365 Roadmap ID 567314, aims to eliminate one of the most persistent friction points for mobile workers who juggle chats, files, and intranet content throughout the day.

When a colleague shares a link to a SharePoint page or a news post in a Teams chat or channel today, tapping it on a phone typically launches the device’s default browser or the standalone SharePoint mobile app. That context switch can break focus, slow down workflows, and sometimes trigger re-authentication if the browser session isn’t active.

With Roadmap ID 567314, the behavior changes. After the update rolls out, those same links will open inside the SharePoint app that lives within Teams—assuming an admin has made that app available. For users who already have the SharePoint app installed in their Teams client, the experience will feel almost invisible: a tap opens the content right where you are, with the full Teams navigation still at your fingertips. No new tabs, no separate app launches, no login hiccups.

The roadmap entry is succinct: “Teams on Android and iOS will open SharePoint page and news links from chats and channels inside the SharePoint app in Teams, when that app is installed.” It applies to both major mobile platforms and covers the two most common shared SharePoint content types: informational pages and curated news articles.

What This Means for You

For the Mobile-First Worker

If you spend half your day glancing at Teams on your phone, this change will make following shared updates dramatically smoother. Imagine a scenario where a project lead drops a link to a status report stored on a SharePoint site. Today, tapping that link might flick you into Safari, where you’re looking at a page stripped of Teams context—no quick way to reply, no docked chat list, and maybe a login prompt. Tomorrow, the same tap keeps you inside Teams, with the report rendered natively and the chat thread a single back-tap away.

The benefit isn’t just psychological. Tests by Microsoft’s own research teams have shown that keeping users inside a single app can reduce task completion times by up to 30% for repetitive information-gathering workflows. For a busy salesperson checking competitive battle cards or a field technician pulling up a troubleshooting wiki, those seconds add up.

For IT and Microsoft 365 Administrators

The change arrives with no toggle to flip—it will be enabled automatically when the underlying service update ships. However, the experience depends on the SharePoint app for Teams being installed either by the user or pushed by policy. If your tenant hasn’t adopted the SharePoint Teams app, users will continue to see link behavior as it is today. Admins should plan to:

  • Review current Teams app setup policies and ensure the SharePoint app is not blocked.
  • Consider deploying the SharePoint app globally via a Teams app setup policy if you want all users to benefit from the in-app experience immediately.
  • Update any internal documentation that tells users to expect browser-based link handling.
  • Monitor the Message Center for the official rollout timeline, as the roadmap entry doesn’t yet specify a release date.

There are no new permissions, data residency implications, or compliance settings tied to this feature—it’s purely a client-side routing improvement. The SharePoint content itself is still rendered securely via the existing SharePoint Online infrastructure.

For Developers and Power Users

If you build Power Apps, SharePoint Framework (SPFx) solutions, or custom intranets, the change shouldn’t break anything. Links generated by your applications will honor the same protocol—they’ll resolve inside the Teams-embedded SharePoint app as long as the link uses standard SharePoint Online URL structures. If you’ve customized deep-link handling in custom mobile apps, you may want to test that the new routing doesn’t collide with any existing redirect rules you’ve set up, though such conflicts are unlikely.

Microsoft’s mobile strategy has, for years, been haunted by the question: which app opens what? The company introduced the concept of “mobile app linking” with Windows Phone, only to abandon it, resurrect it, and refine it again across iOS and Android.

Teams itself has gone through several iterations of link handling. Early versions used an in-app browser that often lacked single sign-on capabilities. Later, Microsoft pushed the dedicated SharePoint mobile app for iOS and Android, encouraging users to install it for best results. But that still meant leaving Teams. The real shift began when Microsoft started embedding first-party “apps” inside the Teams client—a trend that accelerated during the pandemic when remote work forced millions onto mobile devices.

By 2025, the Teams app store included official apps for SharePoint, OneDrive, and Viva Engage, each capable of rendering content natively without leaving the Teams shell. The missing piece was automatic routing: even with the SharePoint app installed, tapping a SharePoint link didn’t necessarily open it in that app. Roadmap 567314 closes that gap. It’s part of a broader pattern: Microsoft recently updated the OneDrive app in Teams to handle clicked file links similarly, and the company’s long-term vision, articulated at Build 2025, is for Teams to become the operating system for collaboration, absorbing all other Microsoft 365 surfaces into its navigation.

What to Do Now

If you’re an end user, there’s nothing to do yet—this feature hasn’t started rolling out. Once it arrives, your best experience will come from having the SharePoint app installed in Teams. Here’s how to check or install it:

  1. Open Teams on your phone.
  2. Tap your profile picture and select Apps.
  3. Search for “SharePoint.”
  4. If it’s listed and you see an Add button, install it.
  5. If it’s already installed, you’re set.

For admins, the proactive steps are slightly different. Use the Teams admin center to:

  • Navigate to Teams apps > Setup policies.
  • Locate the policy assigned to your users (often “Global (Org-wide default)”).
  • Under Installed apps, click Add apps and search for SharePoint.
  • Add it if it isn’t already listed. This pushes the app to users automatically.

Also, bookmark the Microsoft 365 Roadmap page for ID 567314 to track when the feature moves to “Rolling out” status. That’s the signal that the client-side behavior change is live.

What to Watch Next

No launch date appeared on the roadmap as of early July, but standard release cadences suggest a gradual rollout beginning in late Q3 or early Q4 2026. The feature will likely first hit the Teams public preview or Microsoft 365 Targeted Release rings.

Keep an eye out for a companion update that extends the same in-app opening logic to Microsoft Lists, Viva Goals, and other content types hosted on SharePoint, because the underlying technical pattern is the same. When Microsoft draws one link into the Teams tent, others usually follow.