azure-managed-applications

To build a createUiDefinition for Azure Managed Applications, you define UI elements and outputs in a JSON schema that captures user input during deployment. This Skill provides guidance on configuring selectors like StorageAccountSelector and structuring the definition for catalog publishing.

Yes, Azure Managed Applications supports Just-In-Time (JIT) access and managed identities to secure publisher resources. This Skill provides expert guidance on configuring JIT access requests and implementing managed identities for secure cross-tenant deployments.

You can deploy Azure Managed Applications using Bicep by defining your infrastructure as code and publishing it to a service catalog. This Skill offers guidance on Bicep-based catalog deployments, ensuring scalable and governed distribution of reusable Azure components.

Yes, you can integrate Key Vault and customer-managed keys (CMK) with Azure Managed Applications to secure deployed resources. This Skill provides configuration patterns for Key Vault/CMK integration to meet encryption and security requirements.

Azure Managed Applications enforces specific limits and quotas across deployments, including restrictions on managed resource groups and regional capacities. This Skill provides guidance on navigating these constraints and applying security considerations during configuration.

Use Azure Managed Applications when publishing reusable solutions to a service catalog with governed, isolated resources. For cross-tenant management of existing resources, use Azure Lighthouse instead. This Skill focuses on managed applications deployment and configuration, not Lighthouse scenarios.