Ideas worth putting to work.
There’s plenty of Microsoft AI news. Figuring out which updates deserve your attention takes more work.
This edition brings together practical reads from the Healthcare and Life Sciences Blog and other Microsoft teams, covering everyday work, clinical workflows, business apps, and governance.
Recent reading from August 24 through September 22, 2026. Availability reflects the sources available on September 22. Readiness items are labeled separately.
In this edition
- From the HLS blog: choosing Copilot or Cowork, clinical workflows, and meeting governance.
- Beyond the HLS blog: business apps, agent building, and life sciences examples.
- Governance watch: meeting-archive retention.
- One thing to try: brief a colleague on one update.
From the HLS blog
Choose between Copilot and Copilot Cowork
For: business leaders and operations teams
In a September 10 article, Nick (NicholasAquino) compares everyday work you guide step by step with multistep tasks you delegate toward a defined outcome.
Put it to work: Start with a familiar task. Use Copilot to improve a project update; evaluate Cowork when preparing a recurring briefing requires gathering several approved sources. Confirm access, permissions, review points, and usage-based costs before delegating actions.
Read: Copilot or Copilot Cowork, which tool to use and when
Nick (NicholasAquino) | HLS Blog, September 10, 2026. Practical selection guidance, not a new product launch.
Explore AI assistance where clinicians already work
For: clinical leaders and informatics teams
In a September 9 article, sarahgrey explores Dragon Copilot’s focus capability, which brings assistance into the text field where a clinician is working. The examples include reviewing selected information and drafting or refining text without moving everything into a separate application.
The useful starting point is a workflow discussion. Where does your team repeatedly copy information between applications, reformat documentation, or recreate the same type of document?
Put it to work: Choose one example to review with your clinical informatics team. Confirm the capabilities available in your environment and the required clinical review before using patient information.
Read: AI where and when you need it with Dragon Copilot’s ability to focus
sarahgrey | HLS Blog, September 9, 2026. Availability and deployment requirements should be confirmed for your organization.
Review what your AI-assisted meetings leave behind
For: meeting organizers, privacy teams, and Microsoft 365 administrators
On September 3, Michael Goad published a walkthrough of using Copilot only during a Teams meeting without creating a saved transcript.
The governance question extends beyond the recording button. Copilot prompts and responses may still be retained for compliance purposes, depending on your organization’s configuration. Shared notes and other meeting experiences also need their own review.
Put it to work: Before changing meeting policies, bring your privacy, records-management, and IT teams together around one meeting scenario. Decide what information should persist, who should have access, and which experiences are appropriate.
Read: Using Copilot in Sensitive Healthcare Teams Meetings
Michael Goad | HLS Blog, September 3, 2026. An existing-capability walkthrough, not a new feature announcement.
Current Microsoft guidance on Copilot and meeting transcription
Beyond the HLS blog
Describe a business app, then review what it builds
For: operations teams, makers, and IT administrators
On September 10, Ryan Cunningham announced app building in Copilot Studio, with public preview rolling out. The same announcement introduced an /app skill in Copilot Cowork through the Frontier program.
The experience lets you describe an application, review a working preview, and refine it through conversation. Apps can connect to business systems, which makes access and write permissions part of the discussion from the beginning.
Put it to work: A staff-onboarding tracker using fictional records could be a useful first exploration. Define who would use it, what they should see, and which changes they should be allowed to make. Have the appropriate technical owner review the generated application before connecting real organizational data.
Availability: Copilot Studio public preview; the Cowork route is through Frontier. Confirm access in your environment. Building and running apps follows usage-based billing.
Read: Build apps in Copilot Cowork and Copilot Studio
Ryan Cunningham | Microsoft Copilot Blog, September 10, 2026.
Understand what GitHub Copilot brings to Copilot Studio
For: agent builders and the teams funding their work
Jason Moore’s September 2 update explains the GitHub Copilot harness in Copilot Studio. A harness coordinates how an agent uses a model, context, and tools to complete a task.
This is more than connecting a GitHub repository. It gives builders another foundation for agents that reason through multistep business processes, alongside Copilot Studio’s standard harness.
Put it to work: For HLS operations, consider a nonclinical example: reviewing fictional purchase orders and invoices, identifying mismatches, and routing exceptions to a person for approval.
Availability: The underlying harness reached general availability in August. This is September guidance on how to use it, not a September launch. Related capabilities can have separate preview statuses.
Before building: Review capacity and spending controls. Microsoft documents that building, testing, evaluating, and running these agents can consume Copilot Credits; that usage is not included with a user’s Microsoft 365 Copilot license.
Read: GitHub Copilot harness, agent skills, and richer context
Jason Moore | Microsoft Copilot Blog, September 2, 2026.
Review the current cost-management guidance
A life sciences read: AI across research and operations
For: research, manufacturing, and life sciences teams
Jonathon Dreyer’s September 14 industry article looks at how pharmaceutical organizations apply AI across research, manufacturing, and operations.
Put it to work: Select one example and identify the information sources, scientific expertise, and validation your organization would need to explore it. These customer examples are not a promise that another organization will achieve the same results.
Read: How pharmaceutical leaders are operationalizing AI
Jonathon Dreyer | Microsoft Cloud Blog, September 14, 2026. Industry examples, not a product availability announcement.
Governance watch
Meeting archives need a separate retention conversation
For: Teams administrators, privacy, and records-management teams
Microsoft’s public documentation describes AI-generated meeting archives that can preserve meeting insights for AI experiences. The documentation currently identifies this capability as preview for organizations in the Teams TAP program.
One detail deserves attention: deleting or expiring a transcript does not automatically delete its AI archive. Archive expiration and applicable Microsoft Purview retention policies need their own review.
Before rollout: This is a readiness item, not a recommendation to enable the feature today. Review the documented creation conditions, access, retention, and deletion behavior. Confirm applicable rollout information in your organization’s Message Center before planning changes.
Read: AI Archives for Microsoft Teams Meetings
Supporting Microsoft Learn guidance, last updated July 27, 2026.
Follow Roadmap 558933
Roadmap entry updated September 21, 2026; currently in development. Future rollout timing is subject to change.
One thing to try
Prepare a short briefing on one update
Choose one of this edition’s public announcements. In your organization’s approved Copilot experience, try:
I want to explain this Microsoft update to a healthcare operations manager who doesn’t follow AI news. Help me write a short briefing about what changed, one nonclinical task it might help with, and what we should check before trying it.
Use this public announcement: [paste the announcement link].
Read the response alongside the source. Check whether Copilot preserved the availability status and whether its suggested use case is reasonable. If it couldn’t access the page, provide the relevant public excerpt.
Then ask:
Make this shorter and explain any technical terms.
Use public material for this exercise, and review the briefing before sharing it.
If you’re still finding your starting point, visit Get Started with Microsoft AI in Healthcare and Life Sciences for a beginner exercise, learning paths, and governance resources.
Microsoft