weekly.ai-news.cz
The AI week, distilled.
Week 34 · 2026
This week in Microsoft AI

Microsoft consolidates Copilot experiences while GitHub expands agent workflows into chat tools.

Microsoft started rolling out a unified Copilot app across personal, work, and school accounts and began retiring several consumer-facing features. In parallel, GitHub pushed Copilot’s cloud agent deeper into Teams and Slack, while publishing a detailed postmortem for a major outage that affected Copilot availability.

01

Microsoft unifies Copilot into one app and URL

Microsoft is rolling out an updated Copilot app that merges consumer Copilot and Microsoft 365 Copilot into a single experience for personal, work, and school accounts, and it introduces the copilot.cloud.microsoft URL.

  • Plan for identity clarity and user support because one app will serve both managed work accounts and personal accounts on the same device.
  • Update internal documentation, bookmarks, and allowlists to reflect the copilot.cloud.microsoft URL to avoid helpdesk tickets and access issues.
  • Review governance guidance for employee dual-use scenarios so corporate data stays within managed tenants even when users switch accounts.
Source — Microsoft Support Microsoft 365 CopilotEnd-user experience
02

Microsoft starts retiring several Copilot consumer features

Microsoft said Group Chat, Podcasts, and the consumer version of Deep Research will be retired as part of the unified Copilot app transition starting 2026-08-18.

  • Audit internal training materials and adoption campaigns that reference the retired features to prevent user confusion and broken guidance.
  • Confirm whether any business processes or pilot programs rely on the retiring consumer features and migrate users to supported enterprise alternatives.
  • Prepare communications for employees who use Copilot personally on corporate devices so they understand which experiences will disappear and when.
Source — Microsoft Support CopilotRoadmap change
03

Partner Center outlines rollout plan for unified Copilot app

Microsoft’s Partner Center August announcements describe clearer account indicators, a new Copilot URL, and a staged rollout that includes early desktop app previews from 2026-08-18 and broader rollout from mid-September.

  • Use the staged rollout window to validate conditional access, device compliance, and identity prompts before broad employee deployment.
  • Coordinate with your Microsoft partner on end-user comms and packaging to minimize disruption when branding and entry points change.
  • Schedule a short pilot with business-critical user groups to confirm separation of work and personal contexts behaves as expected.
Source — Microsoft Partner Center DeploymentChange management
04

GitHub Copilot cloud agent integrates with Microsoft Teams

GitHub launched shared agentic work with GitHub Copilot inside Microsoft Teams in public preview, enabling Copilot cloud agent sessions from Teams conversations and allowing participants to steer work that can result in pull requests.

  • Define who can trigger agent-driven changes from Teams and require extra approvals for PRs created via the Teams integration to preserve change control.
  • Treat Teams conversations as an operational interface for development work and update audit and retention assumptions accordingly.
  • Pilot the integration with a small number of repositories to validate sandbox behavior, repository permissions, and review workflows.
Source — GitHub Changelog GitHub CopilotTeams
05

GitHub Copilot adds a new Slack experience for agent tasks

GitHub announced a new GitHub Copilot experience in Slack in public preview for Copilot Business and Enterprise, enabling planning, triage, investigations, and pull-request creation from Slack conversations.

  • For Czech enterprises running Slack alongside Microsoft 365, this enables consistent Copilot agent usage without forcing a platform switch to Teams.
  • Set Copilot cloud agent budgets and usage policies before rollout to control spend and prevent runaway automated work.
  • Establish an operating model for incident triage via Slack-based agents so ownership, approvals, and escalation paths remain explicit.
Source — GitHub Changelog GitHub CopilotSlack
06

GitHub explains August 17 outage that hit Copilot

GitHub published a postmortem for an August 17 incident lasting 7 hours 47 minutes that affected github.com, authentication, APIs, Actions, and Copilot, and it described prolonged Copilot recovery worsened by client-side retry loops.

  • Update continuity plans for development teams that depend on Copilot by documenting fallback workflows when Copilot token services or auth degrade.
  • Review retry and backoff behavior in enterprise tooling that calls GitHub APIs to avoid amplifying platform load during recovery events.
  • Use the postmortem detail in vendor risk reviews and internal governance discussions about dependence on cloud AI developer tooling.
Source — GitHub Company News ReliabilityDeveloper platform