Latest / Microsoft 365 Roadmap Rundown / Governance Controls, Teams Resilience, and a Very Busy Purview Schedule

Transcript

Governance Controls, Teams Resilience, and a Very Busy Purview Schedule · Microsoft 365 Roadmap Rundown

• 0:00
  Speaker 1: I love this one. It is basically a digital undo button for that one user who always manages to delete the most critical channel in the company.
• 0:08
  Speaker 2: Oh, there's always one.
• 0:09
  Speaker 1: Always.
• 0:13
  Speaker 3: Welcome to the Roadmap Rundown.
• 0:16
  Speaker 2: The podcast that keeps you up to speed on what's new, what's changing, and what's coming next across Microsoft three sixty five.
• 0:23
  Speaker 3: Let's get into it.
• 0:27
  Speaker 1: Imagine walking into your ediscovery team's office right now and telling them, good news, you now have to manage and search through functionally infinite email archives.
• 0:36
  Speaker 2: Oh, man. They would they would probably just walk right out.
• 0:39
  Speaker 1: Right? I mean, it sounds like a joke, but that isn't a hypothetical scenario anymore. Today, we're looking at an environment where data scale is just it's absolutely exploding.
• 0:48
  Speaker 2: Yeah. And the tools we use to govern all that data are really racing to catch up.
• 0:53
  Speaker 1: Exactly. So welcome to Roadmap Rundown. If you're managing a Microsoft three sixty five environment, you know the update feed literally never stops.
• 1:00
  Speaker 2: It really doesn't.
• 1:01
  Speaker 1: So our mission here is to sort through the latest roadmap sources, extract exactly what is changing, figure out why it actually matters to your operations, and give you the practical takeaways you need.
• 1:13
  Speaker 2: And, you know, looking at the stack of sources we have for this deep dive, there is a really clear thematic tension happening.
• 1:19
  Speaker 1: Oh, totally.
• 1:19
  Speaker 2: Like, on one hand, we're seeing this incredible expansion of AI capabilities and massive data scaling. Yes. But counterbalancing that, Microsoft is rolling out some absolutely essential new administrative controls.
• 1:32
  Speaker 1: Right. So that all this new power doesn't just turn into a complete governance nightmare.
• 1:37
  Speaker 2: Exactly. It is the classic push and pull of productivity versus security.
• 1:42
  Speaker 1: Well, let's start with the foundational shifts in our top stories. We are focusing heavily on major structural changes affecting AI governance, data resilience, and how you build custom agents.
• 1:53
  Speaker 2: Yeah. Big shifts here. Let's start with Purview Data Loss Prevention.
• 1:57
  Speaker 1: Okay.
• 1:58
  Speaker 2: It is officially expanding into Microsoft CoWork.
• 2:00
  Speaker 1: Yeah. And this is a massive governance update. So the core change here is that data security admins can now apply a single unified data loss prevention policy across both Microsoft three sixty five Copilot and Cowork.
• 2:13
  Speaker 2: Which is huge.
• 2:14
  Speaker 1: It is. It means you get the power to actively block sensitive prompts, restrict the use of internally labeled knowledge sources, and even stop sensitive prompts from being routed out to Bing for web searches.
• 2:26
  Speaker 2: So here's why you need to care about this. Yeah. It closes a gigantic security loophole. I always think of this like, well, like hiring a very strict bouncer.
• 2:34
  Speaker 1: A bouncer.
• 2:34
  Speaker 2: Okay. Yeah. Previously, you had this bouncer guarding the front VIP entrance which is Copilot, but the back patio which is co work was just wide open. Right? Anyone could just wander in.
• 2:43
  Speaker 1: Exactly. You do not want your users inadvertently leaking proprietary confidential data out to an external web search just because they happen to use a slightly different chat interface.
• 2:53
  Speaker 2: Yeah. Is the exact risk. Which brings us to your immediate action item or takeaway here. Do not assume your permissions will just magically port over. Ensure your data security team actually updates your existing CoPilot policies to explicitly include and cover your co work environments.
• 3:12
  And speaking of SafetyNets, let's look at disaster recovery. Oh yes. By December 2026, Teams channel backup is adding a thirty day native recovery capability. And this applies to standard, private, and public channels.
• 3:25
  Speaker 1: That is wait. So it's a full rollback?
• 3:26
  Speaker 2: Yeah. It allows you to roll back the channel plus the underlying files and messages to a known good state within that thirty day window.
• 3:33
  Speaker 1: I love this one. It is basically a digital undo button for that one user who always manages to delete the most critical channel in the company.
• 3:41
  Speaker 2: Oh, there's always one.
• 3:42
  Speaker 1: Always. Yeah. Or, you know, worse, for a ransomware situation where things get maliciously encrypted or wiped, operational resilience is the entire game here.
• 3:53
  Speaker 2: Absolutely.
• 3:54
  Speaker 1: You don't have to scramble for a third party backup tool just to restore a simple channel mistake anymore. So make sure you update your organization's disaster recovery documentation to explicitly include this thirty day native window. Your help desk needs to know exactly what they can and cannot recover quickly.
• 4:11
  Speaker 2: It's definitely gonna save a lot of weekend IT panic. That's for sure. Yeah. Now let's shift to how we're actually building inside the ecosystem. Copilot Studio is reshaping agent creation.
• 4:21
  Speaker 1: Okay. How so?
• 4:21
  Speaker 2: Well, rolling out between October and November 2026, Studio is moving to an app first maker experience. But the real structural shift is that agents will now render rich interactive UI right in line using MCP apps.
• 4:36
  Speaker 1: Let me make sure I have this right. MCP is the model context protocol. Correct?
• 4:39
  Speaker 2: Yep. That's the one.
• 4:40
  Speaker 1: So instead of the AI just spitting back a giant wall of plain text, what does this actually look like for the user?
• 4:46
  Speaker 2: Right. Instead of text, the agent can pull up a fully interactive sortable table or like a drill down menu or even a data entry form directly inside the chat interface.
• 4:56
  Speaker 1: Oh, that's cool.
• 4:57
  Speaker 2: Yeah. It essentially builds a micro application inside the conversation on the fly.
• 5:01
  Speaker 1: That removes so much friction. Users can explore and act on data without ever leaving the conversation or switching browser tabs.
• 5:08
  Speaker 2: Yeah. Exactly.
• 5:09
  Speaker 1: So if you have developers or PAW users building custom agents, you need to have them reevaluate their internal agent designs right now. They should be planning to leverage these direct inline UI interactions instead of relying on clunky text outputs.
• 5:24
  Speaker 2: Yeah. And tying right into that protocol, our final top story is that Federated Copilot connectors are marked as launched for April 2026.
• 5:32
  Speaker 1: Launched already. Okay.
• 5:33
  Speaker 2: Yeah. This uses that same model context protocol to bring real time access to third party sources directly into Microsoft three sixty five chat, the researcher agent, and Excel.
• 5:43
  Speaker 1: Okay, but whenever we talk about third party data and AI, the immediate question is always data residency. Does this ingest our external databases into Microsoft servers?
• 5:54
  Speaker 2: See that is the brilliant part, it does not.
• 5:56
  Speaker 1: Oh really?
• 5:57
  Speaker 2: Yeah, it doesn't store or index your customer data in Microsoft services at all. It just uses the specific user's identity to broker a real time connection.
• 6:07
  Speaker 1: Wow. Okay. I think of this like, it's like a translator who sits in the room, reads a highly classified foreign document out loud to you, but is physically prevented from ever making a photocopy or taking notes.
• 6:18
  Speaker 2: That is a great way to look at it.
• 6:20
  Speaker 1: Yeah. The data stays where it lives, but you still get the value of understanding it. It securely brings external data into daily workflows without compromising your data boundaries. So So for the admins listening, you need to get into the Microsoft three sixty five admin center today and review exactly how you want to govern these new external connectors.
• 6:38
  Speaker 2: Definitely. Before your users start trying to hook up every external database they can find.
• 6:42
  Speaker 1: Exactly. So those are the massive architectural shifts, but we also need to see how these ripples are hitting the tools everyone uses every single day.
• 6:50
  Speaker 2: Right. So let's transition from the structural down to the practical everyday workflows in the rundown. Here we'll see how these updates are hitting everything from analytics to virtual desktops.
• 7:00
  Speaker 1: Perfect. Kick us off.
• 7:02
  Speaker 2: Starting with proving the value of all this AI agent analytics in Viva Insights is gaining value insights. We're talking about metrics like estimated assisted hours and the specific types of work agents are handling.
• 7:13
  Speaker 1: That's huge for metrics.
• 7:14
  Speaker 2: Yeah this hits preview in September 2026. I will note though that the broader agent dashboard and the daily metric export features those are shifting their milestones slightly to October and November. November.
• 7:26
  Speaker 1: Got it. But honestly proving the ROI of Copilot is like the single biggest directive for IT leaders right now.
• 7:32
  Speaker 2: A 100%.
• 7:33
  Speaker 1: You have to justify the license cost and this is exactly how you do it. Your action item here is clear. Leaders and adoption specialists need to start actively monitoring the Agent three sixty five dashboard to track the actual quantifiable time these agents are saving your organization.
• 7:49
  Speaker 2: Right. Now moving from AI scale to raw data scale, let's talk about OneDrive for Mac. Okay. Starting in an October 2026 preview, the macOS sync ceiling for qualifying devices is jumping from 300,000 items to a massive 1,000,000 synced items.
• 8:06
  Speaker 1: A million.
• 8:07
  Speaker 2: A million. This requires the insider's ring and specific hardware specifications though.
• 8:11
  Speaker 1: Okay. I have to push back here. 1,000,000 synced files. Is anyone really trying to sync a million individual files on a local Mac drive or is this just a benchmark flex from the engineering team to show what the sync engine can
• 8:23
  Speaker 2: Well, I know it sounds completely excessive for, you know, an individual user. Yeah. But think about enterprise operations.
• 8:28
  Speaker 1: Okay. Like who?
• 8:29
  Speaker 2: You have massive marketing departments or software engineering teams that need to sync organization wide SharePoint document libraries locally to do their jobs. They hit that 300,000 limit much faster than you'd think.
• 8:43
  Speaker 1: Oh, and when they do, the client just crashes.
• 8:45
  Speaker 2: Exactly. The same client just chokes. This natively solved a major scaling issue that previously required incredibly complex workaround architectures.
• 8:55
  Speaker 1: Okay. That makes total sense when you frame it around massive shared libraries rather than individual hoarding. So if you manage those specific high capacity Mac users
• 9:05
  Speaker 2: Yeah.
• 9:05
  Speaker 1: You know, your video editors, your heavy developers, get them opted into the insider's ring if their hardware meets the specs so they can test this out.
• 9:12
  Speaker 2: Yep. Good call.
• 9:13
  Speaker 1: And speaking of drowning in files, what is happening with OneDrive on the web?
• 9:18
  Speaker 2: By August 2026, OneDrive web is rolling out support for multiple simultaneous filters, file type filtering, and it's adopting the modern SharePoint document library layout.
• 9:27
  Speaker 1: Simple, but wildly effective. I mean, it speeds up file retrieval and kills the endless scrolling.
• 9:32
  Speaker 2: Yeah. Nobody likes the endless scroll.
• 9:34
  Speaker 1: Right. The goal here is reducing search fatigue. Make sure you highlight this multi filtering experience in your next end user training or internal newsletter. It's a quick win.
• 9:45
  Speaker 2: Definitely. Moving from our files to our meetings, what's changing with Teams shared files? Well, coming in October 2026, meeting organizers will be able to add relevant files and links for all meeting participants directly to the invite.
• 10:00
  Speaker 1: Okay, pretty standard.
• 10:01
  Speaker 2: But the mechanical shift here is that the AI in the meeting, like the facilitator agent, will specifically use these preloaded files for targeted grounding during the call.
• 10:11
  Speaker 1: Wait. That is brilliant. It gives the AI strict, focused context. Exactly. Instead of the AI trying to guess what you're talking about based on the transcript, you're handing it the exact textbook beforehand.
• 10:21
  This is gonna result in vastly more accurate AI summaries and answers.
• 10:25
  Speaker 2: Yeah. It's a game changer for summaries.
• 10:27
  Speaker 1: So you need to heavily advise your meeting meeting organizers to preload documents. It's not just for the human attendees anymore, it's to prep the AI.
• 10:35
  Speaker 2: Right. Now sticking with meetings, let's talk about the infrastructure holding them up, specifically for town halls.
• 10:41
  Speaker 1: Town halls can be rough on the network.
• 10:42
  Speaker 2: Very, but this is a great performance update rolling out for September 2026. For virtual desktop infrastructure environments VDI that are using the new optimization on windows endpoints, media streams for town hall attendees will now offload directly to the local device via a peer to peer connection.
• 11:00
  Speaker 1: Oh, thank goodness. Anyone who has managed a virtual desktop environment during a company wide all hands meeting knows the absolute pain of resource drains.
• 11:09
  Speaker 2: It brings everything to a halt.
• 11:11
  Speaker 1: It really does. This drastically improves high definition video performance and stops the virtual desktop servers from just melting down. So you absolutely need to verify that this new VDI optimization is toggled on for your Windows endpoints to actually leverage this offloading.
• 11:25
  Speaker 2: Absolutely. Now what about the phone system side of Teams? We have another great infrastructure win here. Call queues auto recording is officially launched. Nice.
• 11:34
  Yeah. Admins can now enable automatic recording and transcription for Teams call queues at the system level. And these recordings are stored neatly in SharePoint and accessed via the Queues app.
• 11:44
  Speaker 1: I love anything that removes manual steps for end users. It ensures compliance and quality assurance on every single queued call without relying on a rep to remember to hit record.
• 11:56
  Speaker 2: Yeah. Because they always forget.
• 11:57
  Speaker 1: Always. The catch here though, and this is your takeaway, you need a Teams premium license for the queues app to actually access this feature. Just be aware of that licensing hurdle.
• 12:07
  Speaker 2: Good flag.
• 12:08
  Speaker 1: Left pivot slightly to the security within our communications.
• 12:12
  Speaker 2: Sure. Rolling out in October 2026, any images containing QR codes that come from external senders will be obscured by default in Teams messaging.
• 12:21
  Speaker 1: Oh, wow.
• 12:22
  Speaker 2: Yeah. Additionally, suspicious message reporting is expanding specifically for government clouds, meaning GCC high and DOD environments.
• 12:30
  Speaker 1: Okay. QR phishing or Quishing as they're calling it is a massive headache for security teams right now because traditional text based filters can't easily read those images.
• 12:39
  Speaker 2: Exactly. Just slip right through.
• 12:40
  Speaker 1: Right. Obscuring them by default breaks that immediate reflexive habit of users just pointing their phones at the screen. But you have to communicate this change. Warn your end users that they aren't experiencing a glitch. They will now need to deliberately and manually reveal external QR codes before scanning them.
• 12:59
  Speaker 2: Communication is key there.
• 13:00
  Speaker 1: Yep. And regarding the government clouds, it makes total sense they get their own distinct reporting ways since their threat matrix and compliance logging are entirely isolated from the commercial tenant space.
• 13:11
  Speaker 2: Exactly. Now, security is one kind of headache, but basic project coordination is a whole other beast.
• 13:17
  Speaker 1: Oh, tell me about it.
• 13:18
  Speaker 2: Let's look at Planner. Between September and November 2026, Planner is getting task history, time aware dates, and plan level time zones. Plus, they're rolling out a refreshed modern interface that includes goals, even in basic plans.
• 13:33
  Speaker 1: I wanna focus on those plan level time zones.
• 13:35
  Speaker 2: Yeah. That's a big one.
• 13:36
  Speaker 1: If you have an engineer in London and a project manager in Seattle and a task is due at 5PM, someone is going to be furious when that deadline is missed because of a time zone mix up.
• 13:46
  Speaker 2: Yep. Happens all the time.
• 13:47
  Speaker 1: This solves so much invisible HR and operational friction for distributed teams. Your move here is to establish a standard operating profugure for global project teams to lock in their planned time zones on day one so everyone is literally operating on the exact same clock.
• 14:06
  Speaker 2: Right. And if Planner organizes the work, Teams Workflows is automating it. By September 2026, you will be able to start a workflow using a form to collect list form data.
• 14:17
  Speaker 1: Nice.
• 14:17
  Speaker 2: You'll also have the ability to add multiple workflow steps when building completely from scratch right inside Teams.
• 14:23
  Speaker 1: This lowers the barrier to entry for no code automation immensely. Instead of jumping out to Power Automate or some third party tool, you're keeping the user right in their flow of work.
• 14:32
  Speaker 2: Exactly. Less context switching.
• 14:34
  Speaker 1: Right. Encourage your power users to start building their data collection forms directly in Teams. But of course, the more we automate, the more data we generate. Which brings us back to compliance.
• 14:43
  Speaker 2: It always comes back to compliance. Right. Let's get into Purview auto labeling. Coming to Purview in September 2026 and GA in October, Purview is expanding its support for larger SharePoint scopes.
• 14:55
  Speaker 1: Okay, what does that mean in practice?
• 14:57
  Speaker 2: It's going to provide better policy management flexibility and richer visibility into what your auto labeling is actually doing across the enterprise.
• 15:03
  Speaker 1: Got it. If you are running a massive compliance environment, you know that flying blind with auto labeling is just terrifying.
• 15:11
  Speaker 2: Oh yeah.
• 15:12
  Speaker 1: You need this validation capability to ensure you aren't accidentally locking down the wrong data at scale. Compliance teams need to map out their strategy now so they are ready to expand their auto labeling stopes the moment this drops.
• 15:25
  Speaker 2: Definitely. Speaking of massive compliance, what is happening in Dynamics three sixty five?
• 15:29
  Speaker 1: Right. Let's look at that.
• 15:31
  Speaker 2: By November 2026, Microsoft is introducing capabilities in Dynamics three sixty five Finance to support Brazil's massive 2027 tax reform. This includes handling the new IS tax type, updated tax assessments, and expanded fiscal note functionality.
• 15:46
  Speaker 1: If you operate in Latin America, this is a non negotiable update. Brazil's tax code is notoriously complex, and a systemic reform like this requires deep software integration. Finance teams operating in Brazil must map their 2027 tax planning directly to these new d three sixty five features immediately because 2027 will be here before you know it.
• 16:07
  Speaker 2: It really will. Finally, let's end this section with something highly visible Copilot and ClipChamp.
• 16:13
  Speaker 1: Oh, this is fun.
• 16:14
  Speaker 2: Yeah. This is fully launched now. ClipChamp is integrating AI voiceovers, text animations, and the ability to generate complete video projects.
• 16:21
  Speaker 1: When you say complete video projects, mean?
• 16:24
  Speaker 2: I mean drafting scripts, selecting visuals, adding narration, all straight from a text prompt right on the start page.
• 16:30
  Speaker 1: Wow. This completely democratizes video production for the enterprise. You no longer need to submit a ticket to a dedicated video editor just to put together a simple professional looking internal update.
• 16:41
  Speaker 2: Yeah, it's so fast.
• 16:42
  Speaker 1: Direct your internal communications and HR teams to start using ClipChamp for quick update videos. It is a massive time saver.
• 16:49
  Speaker 2: That is a lot of new capability arriving. But you know, the roadmap is constantly shifting and sometimes things get delayed or pulled entirely. Let's adjust our calendars in Roadmap Rule.
• 17:00
  Speaker 1: Let's see what is disappearing this time.
• 17:02
  Speaker 2: First up, two planned admin facing features have been explicitly canceled.
• 17:06
  Speaker 1: Okay.
• 17:07
  Speaker 2: The Edge Google Works search banner, which would have seamlessly linked Google searches to Microsoft three sixty five Copilot is dead. Also the plan to put Purview integration directly inside the main Microsoft admin center has been halted.
• 17:22
  Speaker 1: Wait. When a feature gets explicitly canceled like that Edge Google banner, how should admins interpret that? I mean did the underlying technology just fail to work or is this more of a strategic pivot?
• 17:32
  Speaker 2: It's almost always a shift in product strategy. Microsoft evaluates user adoption patterns in those preview rings and sometimes they realize a feature either creates friction, overlaps awkwardly with another tool, or just doesn't fit the desired user flow. The technology usually works fine, the deployment expectation simply changes.
• 17:49
  Speaker 1: That makes total sense. So your takeaway here is highly practical. Go into your deployment trackers, strike these two items off the list right now, and just stop waiting for them.
• 17:59
  Speaker 2: Yep. Moving on, Purview's DLM meter migration is shifting.
• 18:02
  Speaker 1: Okay.
• 18:03
  Speaker 2: Yeah. The billing model transition for retained non Microsoft three sixty five generative AI prompts, meaning how text messages and retained external prompts are calculated for storage billing that's moving back to December 2026.
• 18:16
  Speaker 1: Alright. So this is purely a budgetary impact. It shifts your OpEx cost planning timeline. You need to sit down with your finance partners and recalculate your Q four compliance budgets to account for this transition hitting in December instead of earlier in the fall.
• 18:29
  Speaker 2: Exactly. Next, have delays on Azure PST imports.
• 18:33
  Speaker 1: Oh boy.
• 18:34
  Speaker 2: The worldwide preview for importing legacy PST files from Azure Blob Storage directly into Exchange Online is slipping. The preview moves to October 2026 with general availability moving out to December. And this applies to both standard and government variants.
• 18:48
  Speaker 1: That is frustrating for anyone trying to decommission old legacy servers. It stalls email migration projects that rely on this specific Azure pathway. If you are managing one of those projects, reschedule your pending PST migrations to Azure Blob for late Q4 so your team isn't caught sitting on their hands waiting for the tool to activate.
• 19:06
  Speaker 2: Yeah, don't leave them waiting. And our final roulette item involves authentication. The move from shared secret authentication to certificate based authentication for the Rights Management Service Connector, the RMS connector, is being pushed out to January 2027.
• 19:21
  Speaker 1: You know, shared secrets are essentially just complex passwords, which are inherently less secure than certificate based auth. But while the delay is annoying, it actually gives you a much needed buffer. Use this extra time to get your UnTra app registrations and certificates properly provisioned and tested before January so you aren't scrambling at the deadline.
• 19:38
  Speaker 2: Absolutely. Now that we have adjusted our timelines and crossed off the cancellations, let's lock down the active configurations you need to deal with right now in AdminWatch. These are the immediate practical policy configurations admins must address today.
• 19:53
  Speaker 1: Let's start with how we handle Teams recordings and transcription.
• 19:57
  Speaker 2: Meeting organizers are going to notice a change here. They will now only see automatic recording choices that explicitly align with your admin policies.
• 20:05
  Speaker 1: Makes sense.
• 20:06
  Speaker 2: There is also a new record only option that skips transcription entirely. Furthermore, to align with EU requirements, live captions will now default to off for profanity filtering for any user who hasn't set a specific preference. Plus, admins can now dictate via policy whether profane words are masked in transcripts.
• 20:29
  Speaker 1: Sometimes you want the video, but you really don't want a searchable text document of a highly sensitive brainstorm. And the profanity default change ensures broader accessibility and cultural compliance. You need to audit your meeting policies immediately, ensure your profanity and recording defaults actually match your specific company culture and local legal requirements.
• 20:48
  Speaker 2: Next up we have Purview DLP operating at the network layer.
• 20:52
  Speaker 1: This is a big one.
• 20:53
  Speaker 2: Expected in September 2026, this integrates Purview DLP directly with Entra Global's secure access.
• 21:00
  Speaker 1: Okay.
• 21:01
  Speaker 2: Mechanics wise, it allows organizations to intercept and inspect sensitive files right at the network layer preventing data leakage to untrusted cloud apps before the data even reaches the browser.
• 21:12
  Speaker 1: I look at this kind of like moving airport security. In the old model, security was at the individual boarding gates. That's the browser. This network layer integration moves the metal detectors all the way out to the front doors of the airport. You stop the threat before it even gets into the terminal.
• 21:29
  Speaker 2: That's a great analogy.
• 21:30
  Speaker 1: It's incredible for catching data leakage early. Coordinate with your network team right away to deploy global secure access so you can leverage this architecture.
• 21:37
  Speaker 2: Definitely. Now what's happening with retention capacity? Quite a bit actually. Viva Glint is rolling out deleted user retention controls and Exchange Priority Cleanup is targeting October. But the truly massive news here is that eligible Exchange E5 archive mailboxes are planned to automatically expand beyond their previous 1.5 terabyte hard limit.
• 21:59
  Speaker 1: Wait, beyond 1.5 terabytes? For a single archive? This allows for massive, unprecedented data scale while still respecting precise deletion signals for legal compliance. But make sure your e discovery teams understand they are now dealing with functionally infinite e five mailboxes, they need to ensure their search parameters are incredibly tight or their queries will literally take forever to resolve.
• 22:24
  Speaker 2: Yeah, they'll just sit there spinning. And finally, let's close out AdminWatch with Edge Work Profile policies. Microsoft Edge is expanding its tab and Workspace Organization Assistance, which admins can now control via the tab services enabled policy.
• 22:40
  Speaker 1: Good to have that control.
• 22:41
  Speaker 2: Also, to ensure smooth sign ins, Microsoft three sixty five authentication pop ups in work profiles are now allowed by default and that's governed by the M365 AuthPopsIn work enabled policy.
• 22:53
  Speaker 1: Securing the browser is critical, but making sure the authentication flows don't randomly break and lock users out of their daily tools is exactly why this matters. Push these new edge policies via Intune to your work profiles. Your users get the organization benefits without the daily headache of blocked auth prompts.
• 23:08
  Speaker 2: Exactly. And that covers our Roadmap sources for today.
• 23:12
  Speaker 1: Well, we've covered a massive journey today from sweeping AI governance in Purview all the way down to granular browser tab policies in Edge. But looking holistically at all these sources, I wanna leave you with a provocative final thought.
• 23:25
  Speaker 2: Oh, let's hear it.
• 23:26
  Speaker 1: We just talked about the Exchange e five archive expanding beyond 1.5 terabytes. Right? And earlier, we discussed Mac OneDrive supporting a million locally synced items. Are we moving into an era where the idea of cleaning up data is a completely obsolete concept? Are we just going to accept infinite digital hoarding and rely entirely on AI to navigate the mess for us.
• 23:47
  It is something to seriously think about as you design your storage and retention policies for the next five years. Remember to keep your environment secure and stay curious.
• 23:59
  Speaker 3: Thanks for listening to that Roadmap Rundown. You can find the show notes, roadmap item links, and more at www.roadmaprundown.com. We'll be back next week with another look at what's new, what's changing, and what's coming next across Microsoft three sixty five. Roadmap Rundown uses AI assisted production and synthetic voices based on information from the official Microsoft 365 Roadmap. See you next time.