Service principals for applications in Azure - Time & Space Complexity

Time Complexity: Service principals for applications

O(n)

Understanding Time Complexity

When creating service principals for applications, it's important to understand how the time to complete this task changes as you create more principals.

We want to know how the number of service principals affects the total time and operations needed.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Create multiple service principals for applications
for (let i = 0; i < n; i++) {
  az ad sp create-for-rbac --name "app-sp-" + i
}
    

This sequence creates a service principal for each application by running the create command n times.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Creating a service principal via Azure AD API call.
• How many times: Exactly once per application, so n times.

How Execution Grows With Input

Each new application requires one new service principal creation call, so the total operations grow directly with the number of applications.

Input Size (n)	Approx. API Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The number of operations increases in a straight line as you add more applications.

Final Time Complexity

Time Complexity: O(n)

This means the time and operations needed grow directly in proportion to the number of service principals you create.

Common Mistake

[X] Wrong: "Creating multiple service principals happens all at once, so time stays the same no matter how many I create."

[OK] Correct: Each creation is a separate call and takes time, so more principals mean more total time.

Interview Connect

Understanding how operations scale with input size shows you can plan and predict cloud tasks well, a useful skill in real projects and interviews.

Self-Check

"What if we created service principals in parallel instead of one after another? How would the time complexity change?"

Practice

1. What is the main purpose of a service principal in Azure?

easy

A. To allow applications to access Azure resources securely without user accounts

B. To create user accounts for Azure administrators

C. To monitor network traffic in Azure

D. To store data in Azure Blob Storage

Solution

1. Step 1: Understand service principal role

   A service principal acts like an identity for an application to access Azure resources securely.

2. Step 2: Compare options

   Only To allow applications to access Azure resources securely without user accounts describes this purpose correctly; others describe unrelated Azure features.

3. Final Answer:

   To allow applications to access Azure resources securely without user accounts -> Option A

4. Quick Check:

   Service principal = app identity for secure access [OK]

Hint: Service principals are app identities, not user accounts [OK]

Common Mistakes:

• Confusing service principals with user accounts
• Thinking service principals manage storage or network
• Assuming service principals are for monitoring

2. Which Azure CLI command correctly creates a service principal with contributor role for a specific resource group?

easy

A. az ad sp create --name MyApp --role reader --scopes /subscriptions/123/resourceGroups/MyGroup

B. az sp create --name MyApp --role contributor --scope /resourceGroups/MyGroup

C. az ad create-sp --name MyApp --role admin --scope /subscriptions/123/resourceGroups/MyGroup

D. az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup

Solution

1. Step 1: Identify correct Azure CLI syntax

   The correct command to create a service principal is 'az ad sp create-for-rbac' with parameters for name, role, and scopes.

2. Step 2: Validate options

   az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup uses correct command and parameters. Others have wrong commands, roles, or parameter names.

3. Final Answer:

   az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup -> Option D

4. Quick Check:

   Correct CLI command = az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup [OK]

Hint: Use 'az ad sp create-for-rbac' with correct role and scope [OK]

Common Mistakes:

• Using wrong command like 'az sp create'
• Misspelling 'scopes' or 'scope'
• Assigning incorrect roles like 'admin' or 'reader'

3. Given this Azure CLI output after creating a service principal:

{
  "appId": "abcd-1234",
  "displayName": "MyApp",
  "password": "secret",
  "tenant": "tenant-5678"
}

What does the appId represent?

medium

A. The password to access the service principal

B. The unique identifier for the service principal application

C. The tenant ID where the service principal is created

D. The display name of the Azure subscription

Solution

1. Step 1: Understand Azure CLI output fields

   The 'appId' is the unique ID for the service principal's application identity.

2. Step 2: Match fields to meanings

   'password' is the secret, 'tenant' is the Azure tenant ID, 'displayName' is the name shown.

3. Final Answer:

   The unique identifier for the service principal application -> Option B

4. Quick Check:

   appId = service principal unique ID [OK]

Hint: appId is the app's unique ID, not password or tenant [OK]

Common Mistakes:

• Confusing appId with password or tenant
• Thinking appId is subscription name
• Mixing displayName with appId

4. You run this command to create a service principal:

az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup

But you get an error: Insufficient privileges to complete the operation.
What is the most likely cause?

medium

A. The role 'contributor' does not exist

B. The resource group name is incorrect

C. Your user account lacks permission to create service principals

D. The Azure CLI is not installed

Solution

1. Step 1: Analyze error message

   'Insufficient privileges' means the user does not have rights to create service principals.

2. Step 2: Check other options

   Resource group name errors or missing CLI cause different errors; 'contributor' is a valid role.

3. Final Answer:

   Your user account lacks permission to create service principals -> Option C

4. Quick Check:

   Permission error = user lacks rights [OK]

Hint: Check user permissions if 'Insufficient privileges' error appears [OK]

Common Mistakes:

• Assuming resource group name typo causes privilege error
• Thinking role name is invalid
• Ignoring user permission requirements

5. You want to create a service principal that can only read data from a storage account named mystorage in resource group MyGroup. Which Azure CLI command correctly limits permissions to just that storage account?

hard

A. az ad sp create-for-rbac --name MyApp --role Storage Blob Data Reader --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Storage/storageAccounts/mystorage

B. az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup

C. az ad sp create-for-rbac --name MyApp --role reader --scopes /subscriptions/123

D. az ad sp create-for-rbac --name MyApp --role Storage Account Contributor --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Storage/storageAccounts/mystorage

Solution

1. Step 1: Identify required permission and scope

   To allow only read access to blobs, use role 'Storage Blob Data Reader' scoped to the specific storage account.

2. Step 2: Evaluate options

   az ad sp create-for-rbac --name MyApp --role Storage Blob Data Reader --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Storage/storageAccounts/mystorage uses correct role and precise scope. az ad sp create-for-rbac --name MyApp --role contributor --scopes /subscriptions/123/resourceGroups/MyGroup is too broad (contributor on resource group). az ad sp create-for-rbac --name MyApp --role reader --scopes /subscriptions/123 scopes too wide with reader role. az ad sp create-for-rbac --name MyApp --role Storage Account Contributor --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Storage/storageAccounts/mystorage grants more permissions than needed.

3. Final Answer:

   az ad sp create-for-rbac --name MyApp --role Storage Blob Data Reader --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Storage/storageAccounts/mystorage -> Option A

4. Quick Check:

   Least privilege with correct role and scope = az ad sp create-for-rbac --name MyApp --role Storage Blob Data Reader --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Storage/storageAccounts/mystorage [OK]

Hint: Use least privilege role scoped to exact resource [OK]

Common Mistakes:

• Using broad roles like contributor unnecessarily
• Scoping to resource group instead of specific storage account
• Choosing roles that allow write or delete permissions