![veeam backup to azure step by step veeam backup to azure step by step](https://carysun.azurewebsites.net/wp-content/uploads/2019/02/022019_0312_HowtouseVee3.png)
However, for this scenario to work, you must specify the objectId of the user in the access policy and do not specify the applicationId.įurther, the model of a single mechanism for authentication to both planes has several benefits: For example, Azure PowerShell and the Azure portal. In this, the user accesses the key vault from any application registered in the tenant. Applications can access Key Vault in three ways in both cases:
![veeam backup to azure step by step veeam backup to azure step by step](https://www.xpertstec.com/wp-content/uploads/2020/10/veeam-backup-for-azure-login.jpg)
However, all callers in both planes must register in this tenant and authenticate for accessing the key vault. When creating a key vault in an Azure subscription, it’s automatically gets associated with the Azure AD tenant of the subscription.
![veeam backup to azure step by step veeam backup to azure step by step](https://www.xpertstec.com/wp-content/uploads/2020/10/veeam-add-azure-account-type-640x483.jpg)
![veeam backup to azure step by step veeam backup to azure step by step](https://i0.wp.com/veducate.co.uk/wp-content/uploads/2020/06/Veeam-Backup-for-Azure-Integration-with-Veeam-Backup-and-Replication-Add-external-repository.png)
The applicationId is for identifying the required application and the objectId identifies the user. However, for this scenario to work, both applicationId and objectId must be specified in the access policy.