The most immediate change hitting Microsoft 365 tenants this month is the transformation of the Copilot mobile app into a preview-and-chat surface on iPhone. Starting September 15, 2025, the Microsoft 365 Copilot app for iOS will no longer allow editing of Word, Excel, or PowerPoint files. Instead, users can view documents, read comments, and query Copilot Chat for summaries or insights. To make any edit, they’ll be bounced out to the standalone Word, Excel, or PowerPoint app. iPad users will see the same handoff later, though Microsoft hasn’t pinned down an exact date.

This is not a bug or a feature rollback—it’s a deliberate architectural separation. Microsoft is decoupling the generative AI reasoning layer (Copilot) from the fidelity editing engines (the classic Office apps). The strategy lets the company iterate faster on Copilot’s multi-document grounding and chat capabilities while keeping the editing experience optimized in purpose-built apps. For IT admins, the immediate takeaway is simple: if your mobile workforce edits Office files on iPhones, you must ensure the standalone Word, Excel, and PowerPoint apps are deployed and signed in before the switch. Conditional access and app protection policies also need a fresh audit to make sure the Copilot preview flow and the editor handoff both respect your security posture.

Microsoft Lens Bows Out, Scanning Moves to Copilot

The retirement of Microsoft Lens, announced alongside the Copilot app change, adds another layer of urgency. Lens disappears from iOS and Android on September 15, 2025; the app stops producing new scans after December 15, 2025. Microsoft is funneling all scanning into the Copilot app, which now includes a built-in scanner and a “My Creations” storage area. While this consolidation eliminates one more app from users’ phones, it also means any legacy automation that relied on Lens—such as workflows pushing scans to a specific SharePoint library—will break.

Organizations should inventory devices with Lens installed, export local scans to OneDrive, and push the Copilot app to mobile fleets with clear guidance on the new scanning workflow. For regulated industries, the migration must also preserve retention policies and ensure scanned PII is encrypted at rest. Test the Copilot scanner’s behavior with sensitivity labels before retiring Lens completely; some workflows that previously tagged content automatically may need manual adjustments.

Teams Drops the Legacy Calendar Toggle for Good

On the collaboration front, Microsoft Teams is shedding its legacy calendar toggle once and for all. The unified Microsoft 365 calendar, which already surfaces in the new Outlook for Windows and Outlook on the web, becomes the default Teams calendar experience starting in September. It’s not just a reskin: the new calendar bakes in Microsoft Places for hybrid work planning (who’s in the office, which desk is booked), supports split-view for multiple calendars, and feeds richer data to Copilot. For users accustomed to the old toggle, the change will be jarring—some legacy behaviors vanish or move. Admins should publish a quick-reference map of old-to-new actions and train helpdesk staff on how to handle booking and presence questions tied to Places. Audit any scripts or automation that parse the legacy calendar UI; they may break when the toggle disappears.

SharePoint now houses a centralized Template Gallery with over 50 modern, out-of-the-box page templates, plus support for tenant-level custom templates. The gallery aims to slash design overhead for non-web-authors and enforce brand consistency across intranet pages. But templates are double-edged: they can inadvertently surface cross-site content through embedded queries or widgets if not scoped carefully. Worse, page previews and inline content generated from templates must not bypass sensitivity labels or DLP policies.

Microsoft says the gallery respects those controls, but smart admins will test DLP behavior on template-created pages before broad rollout. A pilot with communications and HR teams—armed with a short, approved template set—should catch most issues. Add a “apply compliance labels” step in template instructions to reduce friction. Finally, treat default templates as opinionated starting points: require metadata discipline so that pages don’t accidentally leak confidential data.

Emoji Reactions Become Workflow Triggers

The most quietly powerful innovation, however, may be the emoji-triggered workflows now rolling out in Teams. The Workflows app can use an emoji reaction on a chat or channel message as a trigger for automated actions. React with ❗ to escalate a support ticket, or 👀 to route a message for legal review. Ready-made templates and a “create from blank” option let teams build custom reaction-to-action flows without leaving the chat. This turns a lightweight social gesture into a low-friction automation trigger, collapsing the gap between noticing a problem and acting on it.

But with power comes governance: workflows that create tickets, send emails, or modify files need approval gates, least-privilege run-as accounts, and full audit logging. Start with a pilot of three emoji triggers mapped to well-defined operational tasks, and expand only after documenting the escalation rules. Instrument audit logging for all automated escalations and message routings.

Coming in October: Network Strength Indicator and SharePoint Workflows

Two more features, slated for October, underscore Microsoft’s convergence play. A Network Strength Indicator will show a three-bar icon in Teams meetings to flag Good, Poor, or Bad network quality, with bandwidth-saving suggestions when things degrade. Participants will also see when others have poor connections, adding context for disruptions. It’s a small but impactful addition for IT teams troubleshooting meeting quality.

SharePoint Workflows will bring the same Power Automate-powered, template-driven automation engine already in Teams to SharePoint sites, finally offering a modern alternative to the creaky legacy SharePoint Designer workflows. Users will be able to create notifications, approvals, and file actions with a few clicks, all from within SharePoint. Both moves are about consistency: consistent signals for meeting health, consistent automation builders across surfaces.

Security, Compliance, and Accessibility Cross-Check

Underpinning all these changes is a security and compliance checklist that can’t wait. The Copilot preview-and-chat flow must not violate data loss prevention: if Copilot can summarize a document, that summary has to inherit the document’s sensitivity label and be subject to the same retention and eDiscovery rules. Test Copilot Chat behavior in a tenant sandbox before enabling it widely.

Emoji workflows that touch regulated data need the same scrutiny as any Power Automate flow—apply environment boundaries and least-privilege run-as accounts. SharePoint templates demand a full DLP and label enforcement test; confirm that page previews don’t circumvent policies. For Lens migration, ensure scanned PII is encrypted at rest and that retention policies follow the content to OneDrive or SharePoint. Accessibility also deserves a check: new calendar and Copilot interfaces must work with screen readers and keyboard navigation, so include accessibility testing in your pilot.

Admin Playbook: Prioritized Actions

Here’s a condensed, prioritized checklist for IT teams to navigate September’s changes with minimal disruption:

Immediate (Now)
- Inventory mobile devices for Copilot and Lens usage; ensure Word, Excel, PowerPoint are deployed to iOS fleets.
- Publish a short user advisory about the Copilot preview→edit handoff and Lens retirement timelines.

Short-term (2–4 weeks)
- Pilot Teams emoji workflows with a helpdesk or ops team; document escalation rules.
- Create tenant SharePoint templates and test DLP, sensitivity labeling, and content bleed risks.
- Update support documentation for the new Teams calendar and Places integration.

Medium-term (1–3 months)
- Update mobile conditional access and app protection policies to cover Copilot preview flows and standalone editor handoffs.
- Prepare short video walkthroughs for the new calendar, Places, and Copilot mobile flows.

Ongoing
- Monitor Microsoft Message Center for schedule changes; staged rollouts may shift dates.
- Retire Lens from device baselines after December 15, 2025.

Weighing the Trade-offs

Microsoft’s September 2025 wave is not a single headline-grabbing feature but a cohesive platform pivot. It separates AI reasoning from content editing, replaces scattered creation tools with centralized templates, and sprinkles lightweight automation triggers across the suite. The strengths are clear: less duplication, faster AI innovation, and a more consistent user experience. However, short-term user friction is inevitable—the two-app handoff on mobile and the removal of familiar toggles will spike helpdesk tickets unless proactively managed. Governance of emoji automations and Copilot Chat summaries expands the policy surface considerably; these must be treated as first-class compliance items.

For organizations willing to do the upfront work—auditing, piloting, training, enforcing policies—the result is less context switching, faster page production, and genuinely helpful Copilot interactions. For those that ignore the changes until users complain, September could be a month of helpdesk pain. The timeline is firm on mobile changes and Lens, fluid elsewhere. Start early, test small, and communicate relentlessly.