Latest / Microsoft 365 Roadmap Rundown / Controls, Consent, and a Lot of Moving Dates

Transcript

Controls, Consent, and a Lot of Moving Dates · Microsoft 365 Roadmap Rundown

• 00;00;00;06 - 00;00;03;12 Speaker 1 - Sam Man that is going to unblock so many frozen deployments. 00;00;03;13 - 00;00;04;12 Speaker 2 - Alex Oh, absolutely. 00;00;04;13 - 00;00;21;17 Speaker 1 - Sam Like if you're an IT director who had to put your copilot role out on ice because you're compliance team, flag the data processing locations, it is time to dust off those deployment plans. You need to update your compliance docs because the barrier has officially been lifted. 00;00;21;20 - 00;00;23;16 Speaker 1 - Sam Welcome to the Roadmap Rundown. 00;00;23;20 - 00;00;30;14 Speaker 2 - Alex The podcast that keeps you up to speed on what's new, what's changing, and what's coming next across Microsoft 365. 00;00;30;17 - 00;00;43;09 Speaker 1 - Sam Let's get into it. Imagine an AI just, you know, deciding to automatically delete a vendor file in your third party HR system entirely on its own. 00;00;43;10 - 00;00;46;12 Speaker 2 - Alex I mean, that sounds like an absolute nightmare for any IT professionals, right? 00;00;46;19 - 00;00;53;28 Speaker 1 - Sam It sounds completely terrifying, but, starting very soon, copilot is actually getting the exact permissions needed to do just that. 00;00;53;29 - 00;00;59;28 Speaker 2 - Alex Yeah, it is. And surprisingly, we're going to explain why that is. Well, actually a massive leap forward for your tenant. 00;00;59;29 - 00;01;08;11 Speaker 1 - Sam Exactly. So welcome to Roadmap Rundown. If you're managing a Microsoft 365 environment, you already know the reality of the job, right? Yeah. 00;01;08;13 - 00;01;09;14 Speaker 2 - Alex The endless updates. 00;01;09;15 - 00;01;19;23 Speaker 1 - Sam Yeah Microsoft just drops this towering stack of roadmap updates, and you are left sifting through like hundreds of technical changes, trying to decipher what actually requires your attention. 00;01;19;23 - 00;01;20;13 Speaker 2 - Alex Which is a lot. 00;01;20;17 - 00;01;30;22 Speaker 1 - Sam It is a lot. Yeah. So that's exactly what we're doing today. We're taking that overwhelming mountain of updates and translating it into a really practical, actionable briefing for you. 00;01;30;24 - 00;01;46;19 Speaker 2 - Alex And, you know, it's completely understandable to feel a sense of fatigue when you look at the sheer volume of changes hitting your tenant every quarter. But the secret to managing this ecosystem isn't, well, it isn't memorizing every single feature. 00;01;46;20 - 00;01;47;22 Speaker 1 - Sam No. Definitely not. 00;01;47;29 - 00;01;58;05 Speaker 2 - Alex It's about spotting the underlying patterns. Yeah. Once you understand the, the architectural direction Microsoft is heading, managing the day to day becomes significantly more predictable. 00;01;58;11 - 00;02;05;04 Speaker 1 - Sam That is the perfect way to look at it, honestly. And we have a really clear path for our deep dive into the sources today. 00;02;05;05 - 00;02;06;17 Speaker 2 - Alex Yeah. And AI structured approach. 00;02;06;18 - 00;02;23;15 Speaker 1 - Sam Exactly. We're going to start by looking at the top stories. So the major architectural and compliance shifts happening at the tenant level. Then from there we'll move into the rundown of daily user experience updates. Take a spin at Roadmap Roulette to see, which heavily anticipated features have been delayed or canceled. 00;02;23;16 - 00;02;24;13 Speaker 2 - Alex Always fun. 00;02;24;15 - 00;02;32;14 Speaker 1 - Sam Always fun. And finally, we will wrap up with the admin wash. So the specific toggles and policies you need to configure right now. 00;02;32;18 - 00;02;41;05 Speaker 2 - Alex It's a very logical progression. We're moving from the broad structural shifts. Yeah all the way down to the like concrete actions you need to take at the help desk level. 00;02;41;06 - 00;02;49;22 Speaker 1 - Sam Yeah. So let's just get right into the structural shifts. The biggest narrative we're seeing in the tenant right now is just how aggressively AI is expanding its reach. 00;02;49;23 - 00;02;50;14 Speaker 2 - Alex Oh, definitely. 00;02;50;15 - 00;03;03;00 Speaker 1 - Sam Like in October of 2026, federated Copilot connectors are officially gaining, right? Update and delete actions. Up until now, these connectors have essentially been read only. Right? 00;03;03;03 - 00;03;07;09 Speaker 2 - Alex Correct. Yeah. And this represents a fundamental evolution in how the AI operates. 00;03;07;16 - 00;03;08;07 Speaker 1 - Sam How so? 00;03;08;10 - 00;03;16;18 Speaker 2 - Alex Well, historically federated copilot connectors, specifically the ones integrating with like external third party services. They were retrieval mechanisms. 00;03;16;18 - 00;03;17;28 Speaker 1 - Sam Right. They just pulled data. 00;03;18;00 - 00;03;24;01 Speaker 2 - Alex Exactly. Copilot could read data, summarize it back to the user. It was essentially a highly advanced search function. 00;03;24;01 - 00;03;24;12 Speaker 1 - Sam Okay. 00;03;24;13 - 00;03;34;08 Speaker 2 - Alex Yeah. But with this update, Copilot chat is being unblocked to actively create new records, update existing fields, or even delete content in those external systems. 00;03;34;10 - 00;03;46;08 Speaker 1 - Sam Wow. Okay, so it's graduating from being like a researcher who fetches books for you to an executive assistant who actually has a corporate credit card and can make purchases on your behalf. 00;03;46;11 - 00;03;48;22 Speaker 2 - Alex That is a really great analogy, actually. 00;03;48;23 - 00;03;58;24 Speaker 1 - Sam But I mean, as an admin, giving an AI a corporate credit card terrifies me. How do we, prevent this from becoming just a total compliance disaster? 00;03;58;25 - 00;04;08;25 Speaker 2 - Alex Well, the mechanism here relies on the user's existing permissions. So copilot can only take actions that the user themselves is or is authorized to take in that third party service. 00;04;08;26 - 00;04;09;23 Speaker 1 - Sam Okay, that makes sense. 00;04;09;24 - 00;04;20;09 Speaker 2 - Alex But more importantly, the system is designed with a mandatory pause. Every single create, update, or delete action requires explicit manual user confirmation before it executes. 00;04;20;10 - 00;04;21;12 Speaker 1 - Sam Oh thank goodness. 00;04;21;12 - 00;04;26;03 Speaker 2 - Alex Right. Copilot cues up the action, but a human actually has to press the button to authorize it. 00;04;26;03 - 00;04;31;11 Speaker 1 - Sam Okay, that makes me feel significantly better. I can't just run silently in the background and wipe out a whole database. 00;04;31;12 - 00;04;32;01 Speaker 2 - Alex Exactly. 00;04;32;03 - 00;04;36;05 Speaker 1 - Sam Operationally, though, what should IT admins be doing about this right now? 00;04;36;10 - 00;05;00;13 Speaker 2 - Alex So your immediate action item is to audit your existing connectors inside the M365 admin center. You have really granular visibility into each connectors. Read and write capabilities. Good. Yeah. And you retain the absolute power to review and disable any connectors that don't align with your organization's internal security policies. So the AI is getting more powerful, but you are still holding the leash. 00;05;00;14 - 00;05;07;24 Speaker 1 - Sam Love that. Okay. Speaking of keeping a tight leash on AI, let's talk about where this AI processing actually happens. 00;05;07;25 - 00;05;08;28 Speaker 2 - Alex Oh yeah, the sovereignty. 00;05;08;28 - 00;05;19;15 Speaker 1 - Sam Stuff, right? In December 2026, Copilot local inferencing is expanding its sovereignty controls. I know data residency has been just a massive thorn in the side for global deployments. 00;05;19;16 - 00;05;26;07 Speaker 2 - Alex It's been a total roadblock for certain regions. Honestly. Yeah. And to understand why this matters, we kind of have to look at what inferencing actually is. 00;05;26;08 - 00;05;27;05 Speaker 1 - Sam Break it down for us. 00;05;27;10 - 00;05;34;14 Speaker 2 - Alex So when a user submits a prompt to copilot, the AI model has to process that text, understand the intent, and generate the response. 00;05;34;14 - 00;05;34;24 Speaker 1 - Sam Right. 00;05;35;00 - 00;05;40;21 Speaker 2 - Alex That processing step is called inferencing. And it requires significant GPU compute power. 00;05;40;23 - 00;05;43;19 Speaker 1 - Sam Which means it has to happen in a massive data center somewhere. 00;05;43;20 - 00;05;53;29 Speaker 2 - Alex Exactly. And previously, that processing might have been routed to a data center outside of a highly regulated region, which is, you know, a hard violation to strict data sovereignty. 00;05;53;29 - 00;06;06;12 Speaker 1 - Sam Laws, right? Like if you're a government agency or a highly regulated financial institution, your data literally cannot cross a geographic border, even for like a few seconds of processing. 00;06;06;12 - 00;06;13;22 Speaker 2 - Alex Spot on. But now that inferencing process will occur strictly within applicable local geographies. 00;06;13;23 - 00;06;16;04 Speaker 1 - Sam Nice. Which regions are we talking about? 00;06;16;06 - 00;06;22;17 Speaker 2 - Alex The initial launch covers Australia, India, the United Arab Emirates, the United Kingdom and the United States. 00;06;22;17 - 00;06;25;22 Speaker 1 - Sam Man, that is going to unblock so many frozen deployments. 00;06;25;25 - 00;06;26;24 Speaker 2 - Alex Oh, absolutely. 00;06;26;25 - 00;06;40;09 Speaker 1 - Sam Like if you're an IT director who had to put your copilot rollout on ice because your compliance team flagged the data processing locations, it is time to dust off those deployment plans. You need to update your compliance docs because the barrier has officially been lifted. 00;06;40;12 - 00;06;47;27 Speaker 2 - Alex Yeah, and we're seeing that same hyper focus on security moving from the regional level down to like the individual meeting level. 00;06;48;04 - 00;06;49;25 Speaker 1 - Sam Oh, right. The teams update. 00;06;49;25 - 00;06;56;08 Speaker 2 - Alex Yeah. In November 2026, teams is introducing conditional access for selected meetings. 00;06;56;16 - 00;07;11;20 Speaker 1 - Sam We're putting a conditional access policy on a single specific meeting. Yep. I can already see the help desk lighting up. Frankly, I mean, imagine a vice president trying to join a critical strategy call five minutes late from an unmanaged iPad at an airport. 00;07;11;20 - 00;07;12;18 Speaker 2 - Alex Yeah, they're going to hit a wall. 00;07;12;19 - 00;07;16;23 Speaker 1 - Sam They just hit a brick wall. Isn't this going to cause chaos? 00;07;16;25 - 00;07;24;20 Speaker 2 - Alex I mean, it might cause friction for that specific vice president in the moment. Sure. But we really have to look at the larger security mechanism here. 00;07;24;21 - 00;07;26;03 Speaker 1 - Sam Okay, tell me more. 00;07;26;06 - 00;07;47;03 Speaker 2 - Alex Historically, conditional access was a broad brush. You applied it to the whole tenant or, you know, to specific apps, right? By allowing administrators to apply policies to individual sensitive meetings, you guarantee that participants meet specific security baselines like device compliance or MFA, before they can even enter the lobby of that specific virtual room. 00;07;47;06 - 00;07;59;09 Speaker 1 - Sam Okay, I see the logic there. It takes the burden off the meeting organizer, like the person running a highly confidential M&A meeting, shouldn't be forced to play bouncer, right? Manually checking if everyone in the room is using a secure device. 00;07;59;09 - 00;08;12;17 Speaker 2 - Alex Precisely. It shifts the security check from a human vulnerability to a strict automated system requirement. High level board meetings or strategy discussions can now have bespoke security wrappers. 00;08;12;17 - 00;08;22;28 Speaker 1 - Sam That's super powerful. All right, switching gears from locking down the environment to actually removing friction for the users, let's move into our run down section and look at how daily workflows are improving. 00;08;22;29 - 00;08;24;01 Speaker 2 - Alex Yeah, some good stuff here. 00;08;24;06 - 00;08;29;11 Speaker 1 - Sam In October 2026, outlook is rolling out Multi-Account search on the web. 00;08;29;13 - 00;08;39;22 Speaker 2 - Alex This is a direct response to how modern work actually happens. I mean, many users juggle their primary inbox alongside shared department mailboxes or maybe project specific accounts. 00;08;39;22 - 00;08;40;20 Speaker 1 - Sam I know I do, right? 00;08;40;27 - 00;08;50;01 Speaker 2 - Alex And searching for a specific communication used to require intensely frustrating context switching. You had to search one inbox, come up empty, navigate to the next search again. 00;08;50;03 - 00;09;07;08 Speaker 1 - Sam It is a massive time sync, but with this update, search results from multiple mailboxes will be seamlessly interwoven into a single ranked list. And honestly, the best part is that users can perform standard email actions like replying or forwarding directly from that combine search view. 00;09;07;09 - 00;09;10;13 Speaker 2 - Alex Yeah, they don't have to navigate back to the original source mailbox at all. 00;09;10;13 - 00;09;13;11 Speaker 1 - Sam Which is just a perfect example of technology getting out of the user's. 00;09;13;11 - 00;09;23;24 Speaker 2 - Alex Way. It really is. And speaking of removing annoyances, teams is pushing out some crucial user experience improvements between now and September 2026. 00;09;23;26 - 00;09;27;14 Speaker 1 - Sam There's one specifically that is going to save my sanity. 00;09;27;14 - 00;09;28;01 Speaker 2 - Alex The pasting. 00;09;28;01 - 00;09;37;07 Speaker 1 - Sam One. Yes, when you paste text into teams, it will finally preserve at mentions and shared contacts. Instead of flattening everything into plain text, right. 00;09;37;07 - 00;09;47;17 Speaker 2 - Alex Because the manual rework required to copy a message, paste it into a new chat, and then meticulously re tag three different people, it was just a constant low level friction point. 00;09;47;18 - 00;09;48;13 Speaker 1 - Sam It was the worst. 00;09;48;14 - 00;09;53;17 Speaker 2 - Alex It's a small fix, but it compounds across thousands of interactions a day for a big organization. 00;09;53;19 - 00;10;00;09 Speaker 1 - Sam Absolutely, yeah. Now the other major teams UX update is a dedicated button to temporarily pause all notifications. 00;10;00;09 - 00;10;01;12 Speaker 2 - Alex Oh, this is a good one. 00;10;01;13 - 00;10;10;05 Speaker 1 - Sam We all know the reality of the Do Not disturb presence status. Users change their status to get some deep work done, and then they completely forget to change it back. 00;10;10;06 - 00;10;13;10 Speaker 2 - Alex Yeah, and they just appear entirely unreachable for the next three days. 00;10;13;11 - 00;10;14;02 Speaker 1 - Sam Exactly. 00;10;14;03 - 00;10;24;10 Speaker 2 - Alex That is exactly why this new button is so valuable. It gives users a time bound way to quiet the noise without permanently altering their present state. 00;10;24;11 - 00;10;25;23 Speaker 1 - Sam That's a great habit to build. 00;10;25;26 - 00;10;39;14 Speaker 2 - Alex Yeah, and for the IT professionals listening, this is an incredibly valuable behavioral tool. Actively teach your users to rely on the pause notifications feature rather than, you know, manually fumbling with their present settings. 00;10;39;16 - 00;10;53;20 Speaker 1 - Sam Speaking of behavioral tools that require some active training in September 2026, Copilot is getting precise highlighting. Yes. Have you ever asked an AI to tweak a single awkward sentence and it enthusiastically decides to rewrite your entire ten page document? 00;10;53;26 - 00;11;19;24 Speaker 2 - Alex Yes, and it completely destroys your workflow when that happens. Yeah. The underlying mechanism here is about context windows. When you give an AI a broad command, it basically looks at the entire document as its playground, right? Precise highlighting solves this by allowing a user to highlight a specific sentence, a single paragraph, or like just one table. When they prompt copilot, the AI restricts its processing strictly to that highlighted selection, so. 00;11;19;24 - 00;11;25;16 Speaker 1 - Sam You can ask it to summarize or translate, or just change the tone of those three specific sentences. 00;11;25;17 - 00;11;26;04 Speaker 2 - Alex Exactly. 00;11;26;07 - 00;11;34;26 Speaker 1 - Sam This is purely a behavioral training opportunity for your organization. You really need to train your users with the phrase highlight before you prompt. 00;11;34;26 - 00;11;36;07 Speaker 2 - Alex Highlight before your prompt. I like. 00;11;36;07 - 00;11;41;24 Speaker 1 - Sam That. Yeah, it constrains the AI and just gives the user vastly superior control over the output. 00;11;41;25 - 00;11;51;06 Speaker 2 - Alex It brings predictability to the AI experience. Yeah. And actually predictability is also at the heart of a major accessibility update coming to teams in December 2026. 00;11;51;07 - 00;11;53;08 Speaker 1 - Sam Oh, the interpreter window. Yeah. 00;11;53;10 - 00;11;58;26 Speaker 2 - Alex They are introducing a persistent pop out video window specifically for sign language interpreters. 00;11;58;28 - 00;12;10;16 Speaker 1 - Sam This is incredibly important. Currently, if you're a deaf or hard of hearing user relying on a sign language interpreter, the dynamic nature of teams meetings kind of works against you. 00;12;10;17 - 00;12;11;00 Speaker 2 - Alex It really. 00;12;11;00 - 00;12;26;20 Speaker 1 - Sam Does. If someone suddenly shares a screen, or if the active speaker changes, the meeting layout shifts automatically. The interpreters video can easily get shuffled out of you into the gallery, which just completely cuts off the user's ability to follow the conversation. Right? 00;12;26;27 - 00;12;37;14 Speaker 2 - Alex And this update elegantly solves that structural problem. And interpreters video or honestly, any participants video you need to keep focus on can be popped out into a separate resizable window. 00;12;37;15 - 00;12;38;14 Speaker 1 - Sam That's brilliant. 00;12;38;16 - 00;12;45;17 Speaker 2 - Alex Yeah, and that window persists across monitors and applications. Yeah, it's entirely immune to whatever layout changes are happening in the main teams meeting. 00;12;45;17 - 00;12;59;02 Speaker 1 - Sam It is a huge accessibility win, and you shouldn't wait for your users to stumble upon this. Proactively communicate this capability to your organization's accessibility resource group so they know this tool is like ready and at their disposal. 00;12;59;05 - 00;13;11;23 Speaker 2 - Alex Definitely. Now, regarding predictability, again, sometimes the system needs to clean up after itself. In October 2026, inactive meeting created planner plans are going to automatically expire. 00;13;11;29 - 00;13;13;28 Speaker 1 - Sam Hold on. Things are just going to auto delete. 00;13;13;29 - 00;13;14;25 Speaker 2 - Alex Well, yes and no. 00;13;15;02 - 00;13;31;04 Speaker 1 - Sam Because if an end user sees the word deleted anywhere near their projects, they're going to submit a severity one helpdesk ticket claiming it just wiped out their entire year's worth of work. How exactly do we trace what is kept versus what is actually removed? 00;13;31;06 - 00;13;41;11 Speaker 2 - Alex Let's clearly define the mechanics so you can reassure your users. This applies specifically to planner plans that are automatically generated via teams meeting notes or Microsoft Loop components. 00;13;41;12 - 00;13;43;13 Speaker 1 - Sam Okay, so just the auto ones, right? 00;13;43;14 - 00;13;51;19 Speaker 2 - Alex If one of those automatically created plans has zero task activity for 180 days, the system flags it as abandoned digital clutter. 00;13;51;22 - 00;13;56;14 Speaker 1 - Sam Got it. So it isn't targeting like a meticulously maintained department project board? 00;13;56;15 - 00;14;04;20 Speaker 2 - Alex Exactly. And more importantly, the actual tasks that were written down inside the loop component and the meeting notes themselves. They remain completely intact and untouched. 00;14;04;22 - 00;14;05;26 Speaker 1 - Sam Oh, phew. Okay. 00;14;05;28 - 00;14;15;26 Speaker 2 - Alex It is only the unused empty planner shell operating in the background that gets removed. The data is safe. The system is just sweeping away the architectural cobwebs. 00;14;15;27 - 00;14;26;24 Speaker 1 - Sam Okay, that makes perfect sense. So your action item here is simply to be prepared with that explanation when users inevitably ask. You can confidently tell them their notes are perfectly safe. 00;14;26;26 - 00;14;27;17 Speaker 2 - Alex Exactly. 00;14;27;19 - 00;14;36;03 Speaker 1 - Sam Which actually brings us to an interesting point about expectations. We build these massive adoption plans around Microsoft's roadmap, but, plans inevitably change. 00;14;36;04 - 00;14;43;19 Speaker 2 - Alex They do. And navigating those changes is critical for maintaining it credibility. Which brings us to the roadmap roulette section. 00;14;43;19 - 00;14;52;05 Speaker 1 - Sam Yes. Let's spin the wheel. We need to examine what is delayed, rolled back, or explicitly canceled so you can adjust your organizational expectation. Right. 00;14;52;10 - 00;14;56;21 Speaker 2 - Alex So story nine covers two heavily anticipated features that have been explicitly canceled. 00;14;56;21 - 00;14;57;16 Speaker 1 - Sam Okay. Let me. 00;14;57;21 - 00;15;04;21 Speaker 2 - Alex First. The built in AI real time interpreter on teams physical phone devices that is not moving forward. 00;15;04;23 - 00;15;17;11 Speaker 1 - Sam Second copilot chat session persistence. That was the feature designed to save your navigation history so you could jump back into an old copilot conversation exactly where you left off. That's also been scrapped. 00;15;17;12 - 00;15;24;10 Speaker 2 - Alex Wow. Okay. Because organizations often build internal hype based on these roadmap promises. 00;15;24;13 - 00;15;25;04 Speaker 1 - Sam All the time. 00;15;25;07 - 00;15;41;05 Speaker 2 - Alex If you had a logistics department eagerly waiting for real time translation on their physical desk phones or, you know, power users banking on persistent copilot chats to manage long term research, they are going to be severely disappointed if you don't reset their expectations right now. 00;15;41;12 - 00;15;50;14 Speaker 1 - Sam It's an exercise in administrative hygiene. Really? Yeah. Go into your internal knowledge base, scrub these features from your training materials and just remove them from any coming soon newsletter. 00;15;50;17 - 00;15;56;21 Speaker 2 - Alex Yeah, if you don't explicitly tell users it isn't coming, they're going to waste your health. Desk's time trying to figure out why they can't find it. 00;15;56;22 - 00;16;07;07 Speaker 1 - Sam Exactly. Now moving to features that technically arrived but were subsequently pulled, Microsoft temporarily rolled back a teams chat organization feature. Oh, I remember this. 00;16;07;14 - 00;16;16;10 Speaker 2 - Alex Yeah, this is the user interface update that automatically group chats into built in sections. It's sort of things like muted chats or meeting chats into neat little categories. 00;16;16;11 - 00;16;28;03 Speaker 1 - Sam So when a UI feature gets rolled back after it actually hits users, is it usually because of like a severe technical bug under the hood, or is it just user backlash because people hate when their buttons move? 00;16;28;06 - 00;16;49;13 Speaker 2 - Alex It's a great question. While the roadmap documentation doesn't specify the exact rationale for this specific rollback, it highlights a crucial reality for IT administration. Agility is just mandatory, right? Some users inevitably saw this new chat interface. They adapted to it and now it has vanished. Your helpdesk is going to get tickets asking where the chat sections went. 00;16;49;15 - 00;16;59;15 Speaker 1 - Sam And you just have to be ready to simply explain that the feature was pulled back for further refinement. It's a really great reminder to not overcommit to preview features in your permanent documentation. 00;16;59;16 - 00;17;19;20 Speaker 2 - Alex Exactly. Now we also have timelines that are simply shifting to the right delays. The target dates for the new Meeting Shared Files feature, which is designed to automatically share relevant files and ground the AI contextually within a meeting. Along with the inline Copilot, mobile search have both been pushed deeper into the fourth quarter of 2026. 00;17;19;24 - 00;17;26;08 Speaker 1 - Sam You know, while delays can be irritating, let's be honest, it actually provides a bit of breathing room for your adoption schedules. 00;17;26;09 - 00;17;26;27 Speaker 2 - Alex It really does. 00;17;27;05 - 00;17;35;21 Speaker 1 - Sam You just got the gift of a little more time to prepare your support desk. And refine your rollout communications. Just adjust your internal calendars accordingly. 00;17;35;22 - 00;17;43;21 Speaker 2 - Alex Preparation is ultimately what defines successful IT administration, which actually brings us to our final focus area the admin watch. 00;17;43;25 - 00;17;54;21 Speaker 1 - Sam Let's do it. We've discussed the architectural shifts we covered. The user experience changes. Now let's talk about the specific administrative controls and policies you actually need to configure to keep the environment safe. 00;17;54;27 - 00;18;12;03 Speaker 2 - Alex Let's start with a major security control arriving in November 2026. Weaponizing file blocking in teams. Up until this point, organizations have largely had to rely on Microsoft's recommended default list of blocked file extensions to prevent, you know, malicious payloads from spreading through teams chats. 00;18;12;03 - 00;18;12;24 Speaker 1 - Sam Right? 00;18;12;26 - 00;18;17;20 Speaker 2 - Alex With this update, administrators are gaining the capability to fully customize that block list. 00;18;17;23 - 00;18;40;01 Speaker 1 - Sam So we are moving away from Microsoft's standardized safety net. Yep. This is huge because it gives organizations the flexibility to align teams protections strictly with their own unique security postures. Like, if your specific industry requires you to block incredibly obscure file types that just aren't on Microsoft's radar, you now have the explicit power to do that. 00;18;40;06 - 00;18;50;20 Speaker 2 - Alex The immediate operational necessity here is collaboration. You need to sit down with your information security team today and review your organization's existing overarching file protection rules. 00;18;50;21 - 00;18;57;14 Speaker 1 - Sam Yeah, you want that custom list of blocked extensions fully drafted and approved. So you're ready to implement it the moment this feature goes live. 00;18;57;15 - 00;19;15;23 Speaker 2 - Alex Exactly. Next up is something that honestly feels like science fiction, but it's arriving in November 2026. Teams express face enrollment. Oh, wow. Yeah. Users will be able to opt in during eligible meetings to let their cameras scan and create a biometric face profile, allowing them to be recognized in physical teams rooms. 00;19;15;25 - 00;19;17;07 Speaker 1 - Sam That is wild. 00;19;17;10 - 00;19;34;11 Speaker 2 - Alex It is the mechanism power some very impressive downstream intelligent features, though if you're sitting in a crowded conference room with five other people, the system will use that biometric profile to correctly identify who is speaking in the meeting transcript and attribute actions appropriately. 00;19;34;14 - 00;19;41;23 Speaker 1 - Sam I mean, it is brilliant technology, but biometrics always make people nervous. It's like giving the conference room a photographic memory of everyone who walks in. 00;19;41;26 - 00;19;54;02 Speaker 2 - Alex Which is exactly why the administrative control here is so critical. Microsoft has designed this so that tenant administrators can enable or disable this entire feature globally. It holds the keys to the engine. 00;19;54;10 - 00;20;00;16 Speaker 1 - Sam But, you know, this isn't a decision it can make in a vacuum. You don't want to just flip a switch on biometric scanning because it's a cool feature. 00;20;00;17 - 00;20;01;13 Speaker 2 - Alex No. Absolutely not. 00;20;01;20 - 00;20;14;09 Speaker 1 - Sam You need to get H.R. Legal and your privacy officers into a room immediately. You have to align on the organizational and legal implications of facial enrollment before you even consider enabling it tenant wide. 00;20;14;10 - 00;20;21;03 Speaker 2 - Alex Navigating user privacy requires extreme care, especially when users themselves are generating security signals. 00;20;21;08 - 00;20;22;23 Speaker 1 - Sam Oh, you mean the reporting feature? 00;20;22;24 - 00;20;37;06 Speaker 2 - Alex Yes. Between September and November 2026, users are going to see new built in buttons, allowing them to directly report suspicious, malicious meetings and unexpected guest invitations right to their IT admin. 00;20;37;08 - 00;20;59;26 Speaker 1 - Sam Crowdsourcing security sounds great in theory. It helps identify, you know, sophisticated impersonation or phishing attempts that automated filters might just miss, right? But for the IT professional listening, this means a veritable firehose of new alerts is about to hit your dashboard. Users will report everything from actual malicious attacks to perfectly legitimate meetings that they just didn't want to attend. 00;20;59;26 - 00;21;07;26 Speaker 2 - Alex Which raises a critical point about operational readiness. If you turn on a reporting feature without a back end process, you're just creating a black hole for alerts. 00;21;07;27 - 00;21;09;05 Speaker 1 - Sam Yeah. That's dangerous. 00;21;09;12 - 00;21;29;25 Speaker 2 - Alex Your security operations center must design the investigation and response workflows before users start clicking that report button. But when a user flags a suspicious meeting, where exactly does that alert root? Which specific analyst is responsible for reviewing it? What is your service level agreement for taking remediation action? 00;21;29;27 - 00;21;32;12 Speaker 1 - Sam You just have to build the plumbing before you turn on the water. 00;21;32;13 - 00;21;33;28 Speaker 2 - Alex Exactly. 00;21;34;00 - 00;21;59;28 Speaker 1 - Sam So let's take a quick look back at the journey we have been on today. We started with the massive architectural evolution of Copilot, gaining the power to actively write, update and delete data and the relief of local inferencing, keeping that data within regional borders. We explored how daily workflows are losing friction with precise AI, highlighting better teams pasting, and crucial accessibility features for sign language interpretation. 00;22;00;03 - 00;22;07;17 Speaker 1 - Sam We navigated the realities of changing roadmaps, scrubbing canceled features from our training docs, and we finished up with concrete administrative. 00;22;07;17 - 00;22;22;03 Speaker 2 - Alex Actions like customizing file blocks, navigating the legalities of face enrollment, and prepping workflows for user reported security threats. You know, if we synthesize everything we've covered today, there is a really clear, overarching narrative I want you to consider. 00;22;22;03 - 00;22;22;27 Speaker 1 - Sam What's that? 00;22;23;00 - 00;22;52;02 Speaker 2 - Alex We are watching two highly potent trends accelerating simultaneously. On one hand, we're entering an era of unprecedented AI autonomy, where tools like the right update and delete connectors allow systems to take independent, delegated actions on behalf of a user. But on the other hand, we are seeing security become hyper granular and incredibly restrictive. Beautifully illustrated by the ability to apply conditional access policies to a single specific meeting. 00;22;52;04 - 00;23;11;20 Speaker 2 - Alex And this raises an important question to leave you with, with features like face enrollment, voice interaction, and copilot actively writing and deleting data on our behalf. The line between software tool and digital colleague is blurring. As an m365 professional, how do you measure and maintain trust when the software starts acting autonomously? 00;23;11;23 - 00;23;23;20 Speaker 1 - Sam That is something to really think about. Thank you for joining us for this roadmap rundown. We know how incredibly valuable your time is, and we hope this deep dive into the sources helps you manage your environment with a lot more confidence and clarity. 00;23;23;21 - 00;23;26;17 Speaker 2 - Alex Keep looking for the patterns in the architecture, everyone. Until next time. 00;23;26;19 - 00;23;32;20 Speaker 1 - Sam Have a fantastic week everyone! 00;23;32;22 - 00;24;01;19 Speaker 1 - Sam Thanks for listening to that roadmap rundown. You can find the show notes, roadmap, item links, and more at Roadmap rundown.com. We'll be back next week with another look at what's new, what's changing, and what's coming next across Microsoft 365. Roadmap rundown uses AI assisted production and synthetic voices based on information from the official Microsoft 365 roadmap. See you next time. 00;24;01;22 - 00;24;02;04 Speaker 1 - Sam At.