Set on each compute resource, this controls which people can attach and what data they reach. Dedicated (once called single user) belongs to a single user or group, standard (once called shared) keeps many users apart from each other, and Auto leaves the choice to the runtime.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Access mode in context, with comparison tables and the common traps.
Terms in this definition
- Set
Secret permission in Key Vault for writing secrets; some older material refers to it as Create.
- Dedicated
Running Azure Functions on an App Service plan, which removes the execution time limit and offers VNet integration on Basic and higher tiers.
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
- Standard deployment type
A Foundry deployment type billed per token that keeps processing of prompts and responses inside the Azure geography of the resource, meeting data residency needs at lower volumes.
Related terms
- No isolation shared
A legacy access mode where code from many users shares one environment and nothing separates them. Admins can block it through the Enforce User Isolation setting, and it is not recommended.
- Standard access mode
An access mode for classic compute in which multiple users can share a cluster and run work at once, kept apart by Lakeguard and governed by Unity Catalog. It is the recommended mode unless a needed feature isn't supported.