Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Enclave uses Azure resources to create and operate community and enclave boundaries. You also pay for any workload resources that you deploy inside your enclaves.
Important
Pricing information in this article is for planning guidance only. Pricing can change and you can review the latest pricing. For an estimate, use the Azure Enclave pricing calculator.
How billing works
Customers pay for:
- Azure Enclave billable meters, such as enclave usage. Verify current meters and rates on the Azure pricing page or with your billing owner.
- Azure resources managed by Azure Enclave to create and operate community and enclave boundaries.
- Workload resources that you deploy inside enclaves, such as virtual machines, Azure Kubernetes Service, Azure App Service web apps, storage accounts, databases, or other Azure services.
Platform-managed resources
Azure Enclave deploys and manages resources that support community and enclave boundaries.
Community managed resources can include:
- Managed resource group
- Managed identity
- Azure Virtual WAN
- Firewall policy and rule collections
- Log Analytics workspace
Enclave managed resources can include:
- Managed resource group
- Azure Virtual Network
- Subnets
- Network security groups
- Managed identity
- Log Analytics workspace
- Optional resources such as Azure Bastion
For more information about managed resources, see What is a community?, What is an enclave?, and What gets deployed.
Azure Enclave resource types
Azure Enclave resource types help create and connect secure boundaries, including communities, enclaves, community endpoints, enclave endpoints, enclave connections, and transit hubs. Azure infrastructure resources deployed or used by those Azure Enclave resource types can incur separate Azure resource charges.
Workload resource charges
Resources that you deploy into workload resource groups are billed according to the pricing model for each Azure service. For example, virtual machines, Azure Kubernetes Service, App Service, databases, storage, and monitoring resources each have their own pricing.
For more information about workload resource groups, see Understand resource groups.