Latest / Microsoft 365 Roadmap Rundown / Copilot Gets Eyes, Agents Get Co-Authors, and Purview Gets Pushed to 2027
Transcript
- Copilot Gets Eyes, Agents Get Co-Authors, and Purview Gets Pushed to 2027 Episode 001 • Transcript • 2026-08-30 Roadmap Rundown Episode Title Copilot Gets Eyes, Agents Get Co-Authors, and Purview Gets Pushed to 2027 Episode Summary This week, Copilot Chat’s ability to use images embedded in files is officially marked as launched, and Copilot Studio is preparing to let makers share agents with viewer and editor access. We also look at a useful new report for cleaning up people-profile data across Microsoft 365. Then, the less cheerful calendar news: Purview adaptive scopes for SharePoint DLP have moved from August 2026 to January 2027. Plus, Teams meeting improvements slide by a month, Copilot mobile push notifications are cancelled, Planner gets more colorful, and New Outlook gets an offline email retention policy. Stories Covered Copilot Chat visual grounding with embedded images is launched Copilot Studio maker-to-maker agent sharing Microsoft 365 people-profile data quality reporting Purview adaptive scopes for SharePoint DLP delayed to January 2027 Teams Rooms Facilitator and the new Teams sharing panel move to October Copilot mobile proactive notifications are cancelled Planner conditional task coloring Viva Engage Campaigns Hub on mobile New Outlook offline email retention defaults for admins Historical PowerPoint roadmap-feed cleanup COLD OPEN SAM: Copilot can now look at the chart in your PowerPoint, understand the screenshot in your Word document, and apparently form an opinion about your process diagram. ALEX: It can interpret embedded visuals, yes. SAM: That is a very calm way to say we’ve given the chat window eyes. ALEX: The useful version is: it can ground a response in both the text and the visual material in supported files. SAM: The less useful version is: please make sure that “final_final_v7_USE_THIS_ONE.pptx” actually is the one you want it to see. INTRO ALEX: Welcome to Roadmap Rundown, the show where we turn the latest Microsoft 365 roadmap changes into the things you might actually need to plan for. SAM: This week: better Copilot context, shared agent building, a small but meaningful admin report, and one compliance feature that has taken a fairly substantial detour on the calendar. ALEX: Let’s get into it. THE RUNDOWN ALEX: The big picture this week is a mix of useful foundations and schedule reality. On the useful side, Copilot Chat is now officially launched with the ability to use images embedded in Word documents, PowerPoint presentations, and PDFs when answering questions. SAM: And that one is immediately practical. A lot of business information is not in the paragraph below the chart. It is in the chart. Or the architecture diagram. Or the screenshot someone pasted into a document three years ago and called “context.” ALEX: Exactly. Roadmap item 560540 says Copilot can interpret embedded images in those files, including charts, diagrams, and screenshots, so responses can be grounded in visual as well as textual context. SAM: Which is a good improvement, with the standard reminder that “it can see more of the file” is not quite the same thing as “it now understands every unlabeled arrow in a ten-year-old Visio export pasted into a PDF.” ALEX: A reasonable distinction. But it should help with genuinely visual questions. If someone asks about the trend shown in a report, or what a diagram is depicting, Copilot Chat has more source material to work with than it did before. SAM: And this is marked as launched now, rather than rolling out, for desktop in the worldwide multi-tenant cloud. So it is no longer just a promising line on a roadmap card. ALEX: Right. For organizations using Copilot Chat against document-heavy work, this is a good prompt to test realistic scenarios: documents with a mix of written narrative and embedded visual evidence. SAM: Try the questions people actually ask: “What is this chart telling me?” “What changed between these two diagrams?” “Summarize the risks in this deck.” Not just, “Please describe this pie chart,” because we have all suffered enough through pie charts already. ALEX: After that good news, we do need to talk about the biggest planning change of the week: Purview adaptive scopes for SharePoint DLP are now listed for general availability in January 2027, moving from August 2026. SAM: So, from “this month, hopefully” to “after the holidays, definitely maybe.” ALEX: The item remains in development. The important point is that the date has changed by five months, and that matters because the capability is meant to dynamically target SharePoint sites for DLP policies. SAM: Which brings us to the very enterprise sentence underneath it: this is designed to avoid having to manually maintain static site lists—and to get past the 100-site static policy limit. ALEX: Yes. It is a scaling feature. Instead of naming sites one by one in a static scope and revisiting that list as the environment changes, adaptive scopes can evaluate site properties such as site URL, site name, or custom site metadata. Sites can be included or excluded as those attributes evolve. SAM: A remarkably sensible idea. Which is why compliance teams that were building a rollout plan around August may have feelings about January. ALEX: They should revisit those plans. We’ll get into the operational side in a moment. BIG DEAL ALEX: Let’s stay with roadmap item 549288: Microsoft Purview Data Loss Prevention adaptive scopes for SharePoint. The roadmap describes this as a dynamic scoping capability for SharePoint DLP. Administrators can target DLP policies based on attributes including site URL, site name, or custom site metadata. Instead of a static list that has to be maintained manually, the scope continuously evaluates those properties. SAM: And that is the key phrase: continuously evaluates. Because static scoping sounds manageable until you have a growing SharePoint environment, project sites appearing, sites getting renamed, sites changing purpose, and half a dozen people asking why the policy does not apply to their new workspace. ALEX: Or why it still applies to a workspace that was repurposed. The whole attraction here is that policy targeting can follow a defined set of site characteristics rather than a manually maintained inventory. SAM: The roadmap specifically says it eliminates the 100-site static policy limit. That makes this more than a convenience feature for larger environments. It can materially change how you design DLP policy coverage. ALEX: It can. A compliance team might want a DLP policy that applies to a category of sites rather than a hand-curated collection. For example, that could be a collection based on a consistent URL pattern, naming convention, or custom metadata—assuming the organization has established and maintained those attributes well enough for them to be trustworthy. SAM: And there is the catch. Adaptive policy targeting is only as tidy as the data it depends on. If your site names are “Project Falcon,” “Project Falcon New,” “Project Falcon Actually New,” and “Do Not Delete,” the automation may be technically impressive but operationally adventurous. ALEX: That is why the delay should not necessarily mean idle time. Organizations that expected to use adaptive scopes at general availability in August should adjust the timeline to January 2027, but they can also use the extra time to examine the attributes they intend to use for targeting. SAM: Not making claims about configuration steps here, because the roadmap does not provide them. But as a planning exercise: identify the site attributes you expect to rely on, check whether they are complete and consistently maintained, and make sure policy owners agree on what the targeting logic should accomplish. ALEX: Exactly. Treat it as policy design and data-quality work, not merely a future switch to turn on. The feature is intended to provide granular, automated targeting. The policy logic still needs to be intelligible to the people responsible for it. SAM: Also, do not miss the date nuance. Preview is listed as February 2026, while general availability has moved from August 2026 to January 2027. This is not the roadmap saying the entire concept has disappeared. ALEX: Correct. It remains in development. The general-availability date changed. That is the fact planners need to work from. SAM: And for anyone preparing communications: say “general availability has moved to January 2027.” Do not say “Microsoft cancelled adaptive scopes” or “the feature is gone.” That would be a much more dramatic meeting, and it would be wrong. ALEX: The practical impact is strongest for organizations whose DLP strategy was waiting on a scalable way to target many SharePoint sites dynamically. If August was a gating point for a broader rollout, move the dependency and revisit any interim approach. SAM: In other words: update the project plan before the project plan updates itself in a steering committee meeting. ALEX: A classic feature of enterprise software. SAM: So the big deal is not that adaptive scopes are less valuable now. In many ways, the roadmap description makes the value very clear. The big deal is that the value is now scheduled for January 2027 general availability, and compliance roadmaps need to reflect that. WORTH KNOWING ALEX: Next up, Copilot Studio is getting maker-to-maker agent sharing. Roadmap item 569475 is listed for preview in September 2026 and general availability in October 2026. SAM: This is one of those features that makes agent building look a little more like actual collaborative work instead of a very lonely craft project conducted across browser tabs. ALEX: The roadmap says makers will be able to share agents with other makers in the new GHCP harness. The roadmap does not explain that term further, so we will not pretend it does. But it is clear about the permissions model. SAM: There are two levels. Agent Viewer can view analytics and evaluations only. Agent Editor can view, edit, configure, share, and publish the agent. ALEX: And the roadmap says the associated security roles are auto-assigned. That distinction between a person who can inspect performance and a person who can make or publish changes is important. SAM: Very important. “Can look at the analytics” and “can publish the agent” are not adjacent responsibilities just because both people own a browser. ALEX: For teams building agents collaboratively, this could bring a clearer handoff model. One maker might focus on reviews, evaluations, and performance observations, while another is responsible for changes and publication. SAM: And it makes governance conversations more concrete. Not “who has access to the agent?” but “who can view its analytics, who can edit it, who can share it further, and who can publish it?” ALEX: The roadmap does not provide broader implementation guidance, but teams can prepare by mapping those responsibilities now. Identify the people who should have view-only insight into agent performance versus those who should be allowed to change configuration and publish. SAM: Because “everyone is an editor while we figure it out” is a phase of life, not a governance model. ALEX: The other worth-knowing item is roadmap 568937, a data quality report for profile data in Microsoft 365 Organizational Data Services. It is listed for preview and general availability in October 2026. SAM: This is perhaps less flashy than a new agent-sharing button, but it may be more foundational. Microsoft is finally putting a spotlight on the quality of the people data behind people experiences and AI experiences. ALEX: The report is intended to help Organizational Data Administrators, People Administrators, and AI Administrators assess the completeness and quality of people attributes available in Microsoft 365. SAM: Which means the fields that answer basic organizational questions: who is this person, where do they sit, how do they relate to the organization, and do the systems trying to help us have usable information? ALEX: The roadmap specifically connects high-quality people data to experiences including People Card, Org Explorer, Microsoft 365 Copilot, and Microsoft 365 Cowork. SAM: Microsoft 365 Cowork gets a mention, and I appreciate that we are all collectively expected to keep up with the naming. Somewhere there is a whiteboard with arrows, a revised brand architecture, and one person whispering, “What if we called it Cowork?” ALEX: But the practical point is strong. AI experiences rely on organizational context. If the underlying attributes are missing or incomplete, the experience can be less useful. SAM: Yes. An AI can be very capable and still not know who the regional lead is if the directory data is a patchwork quilt of blanks, stale job titles, and departments that have not existed since the reorg before last. ALEX: The report is expected to let administrators identify data gaps and improve attribute coverage. It is not a magic cleanup button, based on the roadmap. It is visibility—a way to monitor the health and completeness of the people data. SAM: Which is still a meaningful step. You cannot improve what you cannot see, although Microsoft has historically been happy to offer five separate places where you can see slightly different versions of it. ALEX: For organizations investing in People Card, Org Explorer, Copilot, or Microsoft 365 Cowork, this is worth watching. The roadmap puts a clear connection between data quality and the effectiveness of those experiences. SAM: And it is a good moment to ask who owns people data quality internally. HR? IT? Identity? A business operations team? “Everybody” is usually another way of saying “the spreadsheet has won.” ROADMAP ROULETTE SAM: Time for Roadmap Roulette, where the wheel spins and sometimes lands on “one more month.” ALEX: This week, three Teams-related improvements moved from September to October 2026. SAM: A coordinated calendar adjustment. Honestly, that is almost elegant. ALEX: The first two are Facilitator for in-person meetings in Teams Rooms: roadmap 560700 for Android and roadmap 560318 for Windows. Both have moved from September to October for general availability. SAM: The functionality described is similar on both platforms. In an in-person Teams Rooms meeting, you can invite Facilitator with one tap from the room console. It assists with notes, decisions, and actions. ALEX: The roadmap says the notes can appear on the front-of-room display or touch board. They are available through meeting recap when shared, and if nobody selects them, they are deleted, with no data remaining in the room. SAM: That last detail is useful. Especially in a room setting, people will reasonably want to know what happens to the notes that are briefly visible on the big screen while everyone is arguing about whether that action item was actually assigned. ALEX: These capabilities are listed as available with Teams Rooms Pro. The Android and Windows entries are listed for worldwide multi-tenant and GCC. SAM: And both now say October. So if you had September written on a room modernization plan, move it one box to the right. Calendar management: the true AI assistant. ALEX: The third date move is roadmap 502520, the new sharing panel in Teams meetings. That also moves from September to October 2026. SAM: This one is for desktop and Mac, and it is listed across worldwide multi-tenant, GCC, GCC High, and DoD. Microsoft says the new sharing panel is intended to modernize and simplify tasks such as window sharing, while making sharing options and file sharing easier to discover. ALEX: A familiar goal, because the sharing panel is where a meeting can transition from productive collaboration to someone sharing the wrong window at exactly the wrong moment. SAM: Every Teams user has watched that pause. “I’m just going to share my screen.” Then: a brief expedition through every open application and a document called “Compensation Planning.” ALEX: The roadmap describes it as a redesign for content discovery and sharing. We do not have screenshots or detailed behavior in the entry, but teams should expect a changed experience in that part of the meeting interface when it arrives. SAM: And then we have an actual cancellation, not just a date move. Roadmap 560339 for proactive push notifications in the Microsoft 365 Copilot mobile app is now marked Cancelled. ALEX: The planned feature would have sent push notifications for common productivity workflows, including “Your Day at a Glance” and “Items waiting for you,” linking users into the relevant Copilot response when opened. SAM: It also referenced Copilot Memory. But Microsoft’s update is very direct: it has decided not to move forward with this change at this time. ALEX: This item was intended for Android and iOS in GCC, GCC High, and DoD. If you had been tracking it for those environments, stop planning around the September 2026 date. The item’s status is explicitly Cancelled. SAM: One fewer category of notification competing to inform you that something is waiting for you. Your inbox will continue that work with quiet professionalism. ALEX: We also have a small piece of roadmap-feed housekeeping. Three previously launched PowerPoint Copilot entries for referencing a Loop or Page when creating a presentation have been removed from the roadmap feed. SAM: Those were roadmap IDs 500862, 500863, and 500864—for desktop, web, and Mac respectively. ALEX: They were listed as launched, with a September 2025 general-availability date. Their removal from the feed should not be characterized as a cancellation. SAM: Right. Removed from the roadmap feed is not the same thing as cancelled. A housekeeping change is not a product obituary. QUICK HITS ALEX: A few shorter items to finish the product news. First: Planner conditional coloring, roadmap 569476, is listed for general availability in September 2026 on the web and in Teams. SAM: This lets tasks be highlighted based on selected criteria, including priority, status, and important task details. ALEX: It sounds modest, but visual scanning matters. On a dense plan, helping people spot the urgent or stalled work quickly can make the board easier to use. SAM: Provided everyone does not independently decide that everything is red. That is not a visual-management system. That is a cry for help. ALEX: Next, Viva Engage is getting a Campaigns Hub on mobile. Roadmap 570157 is listed for October 2026 on Android, iOS, and Teams and Surface Devices. SAM: The hub will be available in the Viva Engage app and in Viva Engage in Teams mobile. Employees will be able to discover and participate in organizational campaigns, browse active and completed campaigns, view details, and follow the ones that matter to them. ALEX: It also highlights top and sponsored campaigns. For internal communicators, that creates a centralized mobile destination for campaign discovery. SAM: For employees, it means internal campaigns may follow them all the way to their phones. Convenient for engagement. Potentially impressive for anyone who thought they could escape the campaign by leaving their laptop at home. ALEX: And a reminder from the opening: Copilot Chat visual grounding, roadmap 560540, is now marked Launched. It can use embedded images in Word documents, PowerPoint presentations, and PDFs to inform responses. SAM: The practical test is not whether it can describe a screenshot. The practical test is whether your real document questions become easier to ask and easier to answer when charts, diagrams, and screenshots are part of the source material. WHAT ADMINS SHOULD WATCH ALEX: One admin-focused item this week: New Outlook for Windows is getting an admin policy for the “Days of email to save” setting in Offline options. SAM: Roadmap 570069, listed for November 2026, in worldwide multi-tenant and GCC. ALEX: The policy will let tenant administrators define the default value for how many days of email are saved offline. Administrators can also designate whether end users can change that setting. SAM: The setting itself is under Settings, General, Offline in New Outlook for Windows. Which is a perfectly reasonable place for it, once you know it exists and have already navigated through the maze. ALEX: The roadmap says the policy can set and enforce the value. That gives organizations a way to standardize the offline mail retention setting rather than leaving it entirely to individual user preference. SAM: And listeners may reasonably ask: why should I care how many days of mail someone saves offline? ALEX: Because it is a user-experience and device-behavior setting that organizations may want to manage consistently. The roadmap does not prescribe a preferred number of days, and neither will we. But it gives admins a lever: establish a default, and decide whether users may override it. SAM: Which is a welcome bit of policy clarity. New Outlook has been steadily acquiring the kinds of controls that administrators ask for immediately after users discover a setting on their own. ALEX: For planning, identify whether there is already an organizational expectation around offline email availability. If there is, this November feature may give you a way to express that expectation through policy in New Outlook for Windows. SAM: And if there is not, perhaps decide before the rollout whether you want one. It is always more relaxing to have the policy conversation before the support ticket conversation. ALEX: The other admin watch item is really the thread connecting several stories this week: data quality. For Purview adaptive scopes, the usefulness of automated targeting depends on reliable SharePoint attributes. For the new profile-data report, the usefulness comes from finding gaps in people data. For Copilot Studio sharing, the question is whether access responsibilities are clear. SAM: The shiny feature is rarely the whole project. It is often the point where existing process gaps become visible in high definition. ALEX: That is a good summary. Use these roadmap entries as a reason to inventory the information and ownership models behind the feature, not just the feature itself. PICK OF THE WEEK SAM: My pick this week is the people-profile data quality report, roadmap 568937. ALEX: Good choice. SAM: It is not the flashiest thing on the list. It does not have a dramatic demo moment. Nobody is going to record a reaction video to a profile-attribute completeness report. ALEX: Possibly for the best. SAM: But it addresses something fundamental. Microsoft 365 experiences increasingly rely on organizational data, and AI experiences do too. If a report makes missing or incomplete people attributes easier to identify, that gives admins a practical starting point. ALEX: I agree. It connects directory and profile-data hygiene to user experiences people can see: People Card, Org Explorer, Copilot, and Microsoft 365 Cowork. SAM: And it may help change the conversation from “our organizational data is kind of messy” to “here are the specific gaps affecting the experience.” ALEX: My pick is Copilot Studio maker-to-maker agent sharing, roadmap 569475. It is an early but important sign of a more formal collaboration model for agent development. SAM: Viewer versus Editor is a simple distinction, but it is the right distinction. ALEX: Especially because Editor access includes editing, configuring, sharing, and publishing. Teams can start aligning those permissions with their actual working model before preview arrives in September. SAM: Two good picks this week: clean the data, and do not let every agent collaboration turn into “who clicked Publish?” OUTRO ALEX: That’s the Rundown for the week of August 30, 2026. SAM: Update the Purview timeline, keep an eye on October for Teams changes, and enjoy the rare thrill of a new admin report that may help explain why the people data is behaving strangely. ALEX: Thanks for listening. SAM: See you next week. Show Notes 560540 — Microsoft Copilot (Microsoft 365): Now smarter with visuals: Copilot Chat leverages embedded images for richer, more accurate answers. https://www.microsoft.com/microsoft-365/roadmap?id=560540 549288 — Microsoft Purview: Data Loss Prevention- Adaptive Scopes for DLP for SharePoint https://www.microsoft.com/microsoft-365/roadmap?id=549288 569475 — Microsoft Copilot Studio: Agent Sharing amongst makers https://www.microsoft.com/microsoft-365/roadmap?id=569475 568937 — Microsoft 365 admin center: Data Quality Report for Profile Data https://www.microsoft.com/microsoft-365/roadmap?id=568937 560700 — Microsoft Teams: AI-powered notes for in-person meetings with Facilitator in Teams Rooms on Android https://www.microsoft.com/microsoft-365/roadmap?id=560700 560318 — Microsoft Teams: AI-powered notes for in-person meetings with Facilitator in Teams Rooms on Windows https://www.microsoft.com/microsoft-365/roadmap?id=560318 502520 — Microsoft Teams: New sharing panel in meetings - improved content discovery and ease of sharing https://www.microsoft.com/microsoft-365/roadmap?id=502520 560339 — Microsoft Copilot (Microsoft 365): Proactive push notifications for the Microsoft 365 Copilot mobile app https://www.microsoft.com/microsoft-365/roadmap?id=560339 569476 — Planner: Conditional Coloring https://www.microsoft.com/microsoft-365/roadmap?id=569476 570157 — Microsoft Viva: Campaigns Hub in Engage and Engage in Teams mobile https://www.microsoft.com/microsoft-365/roadmap?id=570157 570069 — Outlook: Offline settings “Days of email to save” admin policy https://www.microsoft.com/microsoft-365/roadmap?id=570069 500862 — Microsoft Copilot (Microsoft 365): Reference a Loop or Page when creating a presentation with Copilot — Desktop https://www.microsoft.com/microsoft-365/roadmap?id=500862 500863 — Microsoft Copilot (Microsoft 365): Reference a Loop or Page when creating a presentation with Copilot — Web https://www.microsoft.com/microsoft-365/roadmap?id=500863 500864 — Microsoft Copilot (Microsoft 365): Reference a Loop or Page when creating a presentation with Copilot — Mac https://www.microsoft.com/microsoft-365/roadmap?id=500864