AI workload
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Any program running in a cloud account whose job involves a model: an agent, a retrieval service, a batch scoring job or an inference endpoint. It gets an identity, permissions, network access and logs like other compute, and it is reviewed on those, not on the model it calls.
An example, sourced
Microsoft documents hosted agents in Foundry Agent Service as workloads you package yourself. You build the agent as a container image and push it to Azure Container Registry. When you deploy, Agent Service pulls the image, assigns a dedicated Microsoft Entra identity, and exposes a dedicated endpoint. Microsoft says you own the code that runs inside the sandbox, while the platform owns the endpoint, identity, scaling and session state around it.
Why it matters here
Splitting responsibility this way tells a reviewer where to look. The platform sets the identity and the endpoint. The builder's code decides what the agent does with them. Both halves need an answer before production. Both halves of that split need an owner named in the review.
Related pages
Sources
Last reviewed 16 Nov 2026.