Azure cloud services and infrastructure
Configure the Azure services behind an application or automation workflow. These guides connect portal settings with code, networking and identity. API Management controls access to model and tool endpoints; landing zones organize shared services; Automation runs scheduled tasks. Use the service-specific walkthroughs below to work through the part you are deploying. The networking guide adds service endpoints, private endpoints and VNet integration to these portal examples. Use it to trace the connection between an application and the Azure service it calls.
Start with the boundary you need to build
Choose an Azure guide by the part of your application you are working on. If requests to models or tools need a common entry point, start with the API Management walkthrough. If your question is where resources and shared services belong, open the landing-zone example. For a repeated administration task, use the Automation runbook guide. Write down the caller, the destination and the identity between them before following the portal steps. That sketch gives you a way to check whether the example fits your own environment.
Make a small test reproducible
Use a separate test resource or a narrowly scoped environment for the first run. Record the resource names, region, identity and expected response. Follow the linked article with its screenshots or code, then repeat the same request after changing one setting. Check a permitted request and a request that should be refused. When investigating a failure, keep the status code and a timestamp so that you can find the matching trace. Remove secrets and personal information before sharing that trace with somebody else.
Review the operating path
After the example works, list what your team would need to operate it: configuration ownership, logs, a way to recognise failure and a procedure for changing or removing the resource. For an AI integration, also keep the model deployment and the chosen endpoint with the test notes. The articles cover different services and publication dates; check the linked product documentation when a portal option differs. Use the archive to find the relevant implementation step, and the search when you already know the service or error you want to investigate.