Performance tuning in Azure is critical and at the same time not an easy task. It is important we put effort and time in it as proper optimization will reduce the resource consumption and cost. With the release of Copilot for Azure SQL, we got a new and promising way to make this effort easier and to get the answers to our questions fast. It sounds tempting to be able to get some copilot-ed help for questions like where the major cost spending is, why and how to reduce it, what are the active connections running right now or what are the top high CPU queries run in the last week? Even if it’s tempting, we still have some doubts using it, is it useful or it is just a funny toy to play with? Shall we trust it or its just yet another fancy tool out there? Come to this session and let's experience together performance tuning with Copilot and let's see what we can rely on and what to expect.