All of that while trying to explain to your non-technical boss how he can browse the voices available at "the Azure thingy" to pick his favourites to then pick and use in the project due relatively soon. Since, of course, you told him the original Cognitive Speech Services (or Speech Services, or Cognitive Services-Speech, or whatever they decided to call it on that specific page) semi-public URL where he could browse the gallery was "speech.microsoft.com" which is now semi-dead with awful loading times that seem some server issue and has been happenning for a few months now. Or tell them to go to the "new foundry" where he might not be able to find the resource or might not have stuff in the regions you were using up until then, or whatever crap this 3.56 trillion-dollar company decides to throw at you to prevent you from using their services.
And all of this is the exploration phase, where you just use the GUIs and copy things around until they work. Then you need to figure out what you did (and more importantly, where) to be able to write some Terraform/OpenTofu or Bicep or similars to try and keep the environment replicable to avoid the excruciating pain of repeating every single step you followed to get it on a working state.
At the very least, Google was nice enough to launch Vertex AI inside GCP for enterprises that have figured that out, and then Google AI Studio as an almost completely separate thing that only is bound to Google Cloud for billing purposes, similar to how Firebase is integrated too.