The Week at a Glance

  • 🔴 Attackers are impersonating your IT support team inside Microsoft Teams to seize enterprise-wide access - Microsoft has documented an active, human-operated campaign that uses Teams external chat to trick employees into granting remote access, then spreads across your network using your own legitimate tools.
  • 🟡 Exchange Server on-premises users face an urgent patching deadline - Starting the second week of September 2026, Microsoft will begin throttling and then blocking email from Exchange 2016/2019 servers that are not at the latest available patch level; any organization running on-premises Exchange must act this week.
  • 🟡 A new wave of privilege-escalation vulnerabilities affects Microsoft Fabric, Azure AD B2C, Copilot Studio, and Azure AI - Multiple newly disclosed CVEs allow unauthorized attackers to elevate privileges across cloud services your organization may rely on; security teams need to assess exposure now.
  • 🟢 Windows memory integrity protection expands by default in October 2026 - Microsoft will automatically enable stronger kernel-level protection on eligible devices, strengthening your security baseline with minimal IT effort required.

Sources: Microsoft Security Blog - Teams IT Support Impersonation · Exchange Team Blog - Throttling and Blocking · Microsoft Security Response Center


Why This Week Matters

The most urgent story this week has nothing to do with software bugs and everything to do with human behavior: attackers have found a reliable path through Microsoft Teams’ external collaboration features, exploiting employee trust in IT support to gain a foothold that can spread across an entire organization. At the same time, organizations running on-premises Exchange Server face a hard deadline this month that could disrupt email flow if missed. Leadership should ensure that both the security team and the infrastructure team have clear owners and timelines on these two items before the week is out.

Sources: Microsoft Security Blog - Teams IT Support Impersonation · Exchange Team Blog - Throttling and Blocking


Risk & Compliance

  • 🔴 IT Support Impersonation via Microsoft Teams: Attackers are posing as IT helpdesk staff in Teams chat to manipulate employees into granting remote access, then using that foothold for lateral movement across the enterprise using legitimate tools; this campaign is active now, closes no perimeter control automatically, and is directly relevant to HIPAA breach notification, SOC 2 availability and confidentiality criteria, and cyber insurance incident-reporting requirements. This is a social-engineering gap in your Zero Trust posture - external identity is reaching employees without adequate friction or verification.

  • 🔴 Exchange 2016/2019 Email Blocking Deadline - Second Week of September 2026: Microsoft will begin throttling and ultimately blocking inbound email from on-premises Exchange servers that are not at the final available patch baseline, starting this week; organizations that have not patched to the latest available cumulative update for Exchange 2016 or 2019 risk email flow disruption between their on-premises environment and Exchange Online.

  • 🟡 Privilege Escalation Vulnerabilities in Fabric, Azure AD B2C, Copilot Studio, and Azure AI Language: Four newly disclosed CVEs allow unauthorized attackers to elevate privileges across Microsoft Fabric, Azure Active Directory B2C, Copilot Studio, and Azure AI Language; organizations using any of these services should verify that Microsoft’s cloud-side mitigations are applied and review privileged access configurations, particularly where these services touch regulated data subject to SOC 2, HIPAA, or CMMC controls.

  • 🟡 ASCII Smuggling Technique Now Bypassing Email Security Filters: An attack technique originally developed to manipulate AI models is now being used to hide malicious content from email security filters; organizations relying on legacy email filtering rules should confirm that their security tooling is updated to detect Unicode-obfuscated payloads, as this technique can evade controls that meet SOC 2 and HIPAA technical safeguard requirements on paper but not in practice.

  • 🟡 Counterfeit Software Installer Campaign Delivering Malware: An active campaign is delivering malware through convincing copies of legitimate software download pages; organizations should reinforce acceptable-use policies around software installation and confirm that endpoint detection is current, particularly for environments where employees download tools independently.

  • 🟡 EWS Retirement: Configure Your AllowedAppIDs List Now: The final phase of Exchange Web Services retirement is approaching, and Microsoft is refining how tenant-level allow lists will be applied; organizations that do not configure their own EWSAllowedAppIDs list risk having access changed in ways that could disrupt business applications that still rely on EWS, and any application dependencies should be identified and migrated or explicitly permitted before Microsoft’s rollout proceeds.

  • 🟡 Purview Endpoint DLP Device Health Dashboard Now Generally Available: A new dashboard lets compliance administrators see which devices are healthy and receiving data loss prevention policy updates, and which are not; organizations with HIPAA, SOC 2, or state privacy law obligations should use this capability to identify gaps in policy coverage across the endpoint fleet.

  • 🟢 Windows Memory Integrity Protection Expanding by Default - October 2026: Starting in October, Microsoft will automatically enable kernel-level memory integrity on eligible Windows devices, strengthening the security baseline without requiring additional configuration; IT teams should verify device eligibility in advance to ensure the rollout proceeds smoothly and to identify any legacy hardware that may be excluded.

  • 🟢 Microsoft Teams QR Code Protection from External Senders - October 2026: Teams will automatically obscure QR codes sent by external users, requiring employees to consciously reveal them before scanning; this reduces exposure to QR-code phishing with no configuration required.

Sources: Microsoft Security Blog · Microsoft Security Response Center · Exchange Team Blog


What Your Employees Will Notice

  • Copilot gets more powerful AI models this week. OpenAI GPT-6 Astra and Anthropic Claude Fable 5.1 are now available inside Microsoft Copilot for users with Copilot licenses. Employees can delegate larger, more complex tasks to Copilot rather than guiding it step by step. Users working in Copilot Cowork or Copilot Studio may notice different response styles depending on which model they select.
  • QR codes from external Teams contacts will look different starting October. When an outside party sends a QR code in a Teams message, it will appear blurred until the employee actively clicks to reveal it. This is a protective feature, not a bug; communicate proactively to prevent help desk calls.
  • OneDrive web gets a refreshed look and improved file filtering. Employees will see a modernized file browsing experience with multi-filter support across Home, Shared, and folder views. No action is required; brief teams who manage large file libraries that the layout will change.
  • Planner is now available as a tab in private and shared Teams channels. Teams using private or shared channels for sensitive projects can now embed Planner directly, enabling task management without leaving the channel.
  • Meeting organizers will have clearer, policy-aligned recording and transcription options starting November. Meeting Options will only show choices that are actually permitted by your organization’s policies, reducing confusion about what is allowed. A new “Record only” option gives organizers more granular control.
  • SharePoint news can now be cross-posted directly to Viva Engage. Internal communicators can now distribute SharePoint news posts into Viva Engage communities, with comments and reactions synchronized across both platforms.

Sources: M365 Copilot Blog - August What’s New · M365 Roadmap - QR Code Protection · SharePoint Blog - Viva Engage Cross-posting


What Your Help Desk Should Expect

  • Spike in “blurred QR code” tickets from Teams users once October arrives; brief your help desk now so they can explain the new protective behavior rather than escalating as a bug.
  • Inquiries about new AI models in Copilot. Employees may ask which model to use for which task, or report unexpected behavior when switching between GPT-6 Astra and Claude Fable 5.1. Prepare a brief FAQ distinguishing the two.
  • OneDrive layout confusion. The refreshed file browsing interface will generate “where did X go?” contacts from users accustomed to the current layout; a proactive communication or short tip sheet can reduce volume significantly.
  • Teams recording and transcription confusion. Ahead of the November change, some meeting organizers may notice options they previously saw are no longer available; help desk should understand that this reflects policy alignment, not a malfunction.
  • Software installation questions may increase as awareness of the counterfeit installer campaign spreads; help desk should be prepared to verify whether a requested download is legitimate and know the escalation path if malware is suspected.
  • Tickets related to Exchange email flow disruption if your organization runs on-premises Exchange 2016/2019 and patching is not completed before Microsoft’s enforcement begins this week.

Sources: M365 Roadmap - Teams Recording Options · M365 Roadmap - QR Code Protection · Exchange Team Blog - Throttling and Blocking


Cost & Licensing

  • GPT-6 Astra and Claude Fable 5.1 are now available within existing Copilot licenses via Copilot Cowork and Copilot Studio. No new license SKU is required to access these models, but organizations that have not yet licensed Microsoft 365 Copilot should note that these capabilities are part of the Copilot subscription, not the base Microsoft 365 license.
  • Copilot Studio usage costs may increase as employees and developers begin delegating larger, longer-running tasks to the new frontier models; Copilot Studio is metered by the message and by agent activity, so organizations should review their current consumption baselines and set budget alerts before broader rollout of agentic workflows.
  • Exchange Server patching carries implicit cost. Organizations running Exchange 2016/2019 on-premises may need emergency change-control approval and IT resource allocation this week to apply the required cumulative update before Microsoft’s enforcement window opens. Factor in potential downtime windows.

Sources: M365 Copilot Blog - GPT-6 Astra · M365 Copilot Blog - Claude Fable 5.1 · Exchange Team Blog - Throttling and Blocking


Planning Horizon

  • This week - Exchange 2016/2019 Patching Deadline: Confirm with your infrastructure team whether on-premises Exchange servers are at the required cumulative update level; if not, authorize emergency patching before Microsoft begins throttling inbound connections this week.

  • This week - Teams IT Support Impersonation Campaign Response: Direct your security team to review Microsoft’s indicators of compromise and confirm that Defender XDR detections are enabled; separately, authorize a brief all-staff communication reminding employees that IT support will never contact them unsolicited through Teams to request remote access.

  • Within 30 days - EWS AllowedAppIDs Configuration: Assign an owner to audit which business applications still use Exchange Web Services and configure a tenant-managed allow list before Microsoft applies its own defaults, which could cut off unlisted applications without warning.

  • Within 30 days - Privilege Escalation CVE Review - Fabric, Azure AD B2C, Copilot Studio, Azure AI: Ask your security team to confirm cloud-side mitigations are in place and review privileged role assignments across these services, particularly where they interact with regulated data; this is a least-privilege enforcement opportunity across your cloud identity posture.

  • Within 30 days - Purview Auto-labeling Enhancements Preview: Preview of expanded auto-labeling capabilities for SharePoint enters in September; organizations with active data classification programs should enroll in preview to validate labeling at scale before the October GA date.

  • Before October 2026 - Windows Memory Integrity Rollout Preparation: Ask your endpoint management team to identify which devices in the fleet are eligible for automatic memory integrity enablement and flag any legacy hardware or specialized workstations that may be incompatible, to prevent unexpected disruption in October.

  • Before October 2026 - Microsoft Edge Tab Organization and Notification Protection Rollout: Review the new TabServicesEnabled policy if your organization uses managed Edge deployments; the automatic unsubscription from malicious notification sources is a welcome security enhancement but IT should confirm it aligns with any custom browser configurations.

  • Before November 2026 - Purview Information Protection File Labeler for macOS: Organizations with Mac-using employees and active sensitivity labeling programs should plan to deploy the new macOS File Labeler and Viewer when it reaches GA in November; this closes a platform gap relevant to HIPAA, CMMC, and data classification compliance on Apple devices.

  • Before November 2026 - Teams Meeting Recording and Transcription Policy Alignment: Review current meeting recording and transcription policies before the November rollout changes what organizers see in Meeting Options, and confirm that policies reflect current compliance and HR requirements around meeting capture.

Sources: Exchange Team Blog · Microsoft Security Blog · M365 Roadmap


If You Take No Action

On the Teams IT Support Impersonation campaign: Employees who receive a convincing Teams message from someone claiming to be IT support have no way to know it is fraudulent without explicit guidance. If no communication is issued and no detection controls are confirmed, a single compromised employee session can provide attackers with lateral movement access across your entire environment. This scenario triggers breach notification obligations under HIPAA and SOC 2, and many cyber insurance policies require demonstrable controls against social engineering; absence of those controls can affect claim eligibility.

On the Exchange 2016/2019 patching deadline: If on-premises Exchange servers are not updated to the required cumulative update level before Microsoft’s enforcement window opens this week, email flow between your on-premises environment and Exchange Online will be throttled and eventually blocked. The business impact is a disruption to inbound and outbound email for any users or systems routing through those servers, with no grace period once blocking begins.

On the EWS AllowedAppIDs configuration: If your organization does not configure its own allowed-application list before Microsoft applies its defaults during the EWS retirement process, business applications that depend on EWS - potentially including calendar integrations, room-booking systems, or third-party connectors - may lose access without warning. Recovery requires identifying affected applications under pressure and reconfiguring access, which is significantly harder to do during an outage than in advance.

Sources: Microsoft Security Blog - Teams Impersonation · Exchange Team Blog - Throttling and Blocking · Exchange Team Blog - EWS AllowedAppIDs