Introduction
Three separate “Action Required” banners have shown up in our clients’ Azure portals in the past month — one on storage, one on TLS configuration, and one on Copilot. None of them are urgent in the sense of “fix this today,” but each one has a real deadline attached, and the kind of deadline that’s easy to miss if it’s buried in a portal notification instead of a change-management ticket. This briefing walks through all three: what’s changing, who’s affected, and what to put on your team’s calendar now rather than the week before the cutoff.
1. GPv1 Storage Account Retirement
| DEADLINE: 13 October 2026 |
Microsoft is retiring General Purpose v1 (GPv1) storage accounts and recommends migrating them to General Purpose v2 (GPv2). GPv2 offers improved capabilities, better scalability, and access to the latest Azure Storage features. This advisory applies only to GPv1 accounts — StorageV2, FileStorage, and BlockBlobStorage accounts are not affected.
Administrator checklist
- Inventory all Azure Storage accounts.
- Identify GPv1 storage accounts.
- Plan migration to GPv2 before the deadline.
- Validate applications after migration.
2. Azure App Service — Minimum TLS Version
| DEADLINE: 31 May 2027 |
Microsoft is requiring Azure App Service resources to use a minimum TLS version of 1.2 or later. This doesn’t mean TLS 1.2 only newer supported versions remain acceptable. Before changing the minimum TLS version, confirm that all applications, integrations, and clients are compatible, so the change doesn’t cause a service disruption.
Administrator checklist
- Review the minimum TLS version configured for each App Service.
- Identify clients still using TLS 1.0 or TLS 1.1.
- Validate application compatibility.
- Configure the minimum TLS version to 1.2 or later.
3. Azure Copilot Agent Access Changes
| EFFECTIVE DATE: 1 August 2026 |
Starting 1 August 2026, Azure Copilot moves from a single “Agent mode” experience to individual agents, each with its own General Availability or Public Preview status. For tenants that already have Azure Copilot enabled, all agents including Public Preview ones will be turned on by default. The tenant-level Azure Copilot setting is still the master switch: if Copilot is disabled for your tenant today, its agents stay disabled after the change.
Feature availability beginning 1 August 2026
General Availability: Observability Agent.
Public Preview: Deployment Agent, Troubleshooting Agent, Optimization Agent, Resiliency Agent, and Migration Agent.
The Deployment, Troubleshooting, Optimization, and Resiliency Agents are accessed directly from the Azure Copilot chat experience. The Observability Agent and Migration Agent continue to live in their existing homes Azure Monitor and Azure Migrate, respectively.
Changes to agent administration
The prior sign-up process for requesting agent access goes away on 1 August 2026, along with tenant allowlisting. Instead, administrators enable or disable individual agents directly in the Azure Copilot Admin Center.
Administrator checklist
- Want all agents enabled? No action needed that’s the default.
- Don’t want agents on by default? Disable Azure Copilot for your tenant before 1 August 2026.
- On or after 1 August 2026, manage individual agent access in the Azure Copilot Admin Center.
- Questions go to the Azure Copilot team at AzureCopilotPMs@microsoft.com.
Quick Summary
| Advisory | Date | What to watch for |
| GPv1 Storage Retirement | 13 Oct 2026 (deadline) | Only GPv1 accounts are affected confirm your inventory before assuming you need to act. |
| App Service Minimum TLS | 31 May 2027 (deadline) | Longest runway of the three good candidate to bundle into a routine maintenance window. |
| Copilot Agent Access | 1 Aug 2026 (effective date) | The only one of the three where doing nothing is itself a decision agents turn on by default. |
Final Thoughts
These three advisories have very different shapes a hard infrastructure cutoff, a long-lead security configuration change, and a default-on feature rollout which is exactly why they’re easy to lose track of individually. Put each one on your organization’s change calendar now, assign an owner, and treat the Copilot item differently from the other two: it’s the one where silence is itself a choice.
If your team wants a second set of eyes on any of these — an inventory pass on storage accounts, a TLS compatibility check, or a Copilot governance review — AnaData’s Cloud & AI practice can help you scope it.