Pre-requisites for Azure workspace onboarding

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Pre-requisites for Azure workspace onboarding

L2 Linker
  1. To run CyberArk scripts in Azure to create app registrations etc, it requires Azure Shell Cloud. To use Azure Shell cloud, it requires a storage account. Does the workspace onboarding requires a storage account in Azure or works without it? If it requires, can we have it temporarily while running the scripts and delete it later?
  2. It requires the user to be a Global Administrator. Does the user need to be directly added to Global administrator or can be permissioned via a group nested under it?

 

Could anyone please help with these queries?

 

Thanks!

Neha

1 accepted solution

Accepted Solutions

L2 Linker

Hi Neha

I’ve looked into the prerequisites for you regarding the Azure workspace onboarding. Here is the breakdown to help you move forward with the script:

1. Regarding the Storage Account (Azure Cloud Shell) The requirement for a storage account is actually an Azure Cloud Shell requirement, not a CyberArk one.

  • Is it mandatory? If you choose to run the script via the Azure Cloud Shell in your browser, Azure requires a storage account to host your session files.
  • Can it be temporary? Yes. You only need it for the 15–30 minutes it takes to run the onboarding script. Once the script completes and the connection is verified in the CyberArk portal, you can safely delete the storage account. The integration relies on an App Registration, not the storage account, to function long-term.

2. Regarding Global Administrator & Group Nesting

  • Role Requirement: You do need Global Administrator rights to create the necessary App Registrations and grant API permissions.
  • The "Nesting" Rule: It is important to note that Microsoft Entra ID (Azure AD) does not support nested group inheritance for administrative roles.
  • The Fix: The user running the script must be a direct member of the group that has the Global Admin role assigned. If your user is in a group that is nested inside another group, the script will likely fail.

Summary Recommendation: To ensure a smooth onboarding, I recommend assigning the Global Admin role to the user directly (or via a first-level group) and creating a temporary storage account for the Cloud Shell. You can decommission both the role and the storage account as soon as the workspace shows as 'Connected.'

 

Hope it helps.

View solution in original post

1 REPLY 1

L2 Linker

Hi Neha

I’ve looked into the prerequisites for you regarding the Azure workspace onboarding. Here is the breakdown to help you move forward with the script:

1. Regarding the Storage Account (Azure Cloud Shell) The requirement for a storage account is actually an Azure Cloud Shell requirement, not a CyberArk one.

  • Is it mandatory? If you choose to run the script via the Azure Cloud Shell in your browser, Azure requires a storage account to host your session files.
  • Can it be temporary? Yes. You only need it for the 15–30 minutes it takes to run the onboarding script. Once the script completes and the connection is verified in the CyberArk portal, you can safely delete the storage account. The integration relies on an App Registration, not the storage account, to function long-term.

2. Regarding Global Administrator & Group Nesting

  • Role Requirement: You do need Global Administrator rights to create the necessary App Registrations and grant API permissions.
  • The "Nesting" Rule: It is important to note that Microsoft Entra ID (Azure AD) does not support nested group inheritance for administrative roles.
  • The Fix: The user running the script must be a direct member of the group that has the Global Admin role assigned. If your user is in a group that is nested inside another group, the script will likely fail.

Summary Recommendation: To ensure a smooth onboarding, I recommend assigning the Global Admin role to the user directly (or via a first-level group) and creating a temporary storage account for the Cloud Shell. You can decommission both the role and the storage account as soon as the workspace shows as 'Connected.'

 

Hope it helps.

  • 1 accepted solution
  • 70 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!