Azure Copilot is evolving from a conversational interface into a fleet of specialised agents for investigating, troubleshooting, deploying, optimising, and operating the cloud. Modern applications generate an overwhelming volume of telemetry, configuration data, and operational context, far more than any human can absorb, correlate, and act on at the speed modern cloud operations require. Copilot does much of the heavy investigative lifting, turning a sky full of signals into a clear forecast: findings, plans, and proposed actions. Yet the captain still makes the call.
This session takes a practical, demo-led look at operating with Azure Copilot, drawing on my experience as an Azure MVP providing feedback to the team building Copilot since its earliest days. We will explore the current agents, examine what each one delivers in practice (an explanation, a plan, a script, or a pull request), and see exactly where the approval gate sits before anything changes in your environment.
Operating with Copilot also means understanding the control tower: who is cleared for take-off through admin controls; what Copilot can access and act on through your identity, RBAC, Azure Policy, and resource locks; and how BYOS retains every Copilot interaction in your own environment for audit and governance.
Packed with the latest capabilities announced at Microsoft Ignite, this session covers where Copilot is heading as well as what you can use today. You will leave knowing what Copilot can do for you, how to roll it out safely from day one, and where the captain's seat remains yours.

This is a session placeholder based on private preview conversations with the Copilot team. Between now and the conference more information may be publicly disclosed about the service which will mean a further enhanced public session description. TBA, so to say. ;~)