Service principals for applications in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a service principal in Azure?

A service principal is like a user identity for an application. It allows the app to access Azure resources securely without using a real person's login.

beginner

Why use a service principal instead of a user account for app access?

Service principals provide controlled, limited access to resources. They avoid using personal user credentials, improving security and automation.

intermediate

How do you create a service principal in Azure?

You create a service principal by registering an application in Azure Active Directory and then creating a service principal for it. This can be done via Azure Portal, CLI, or PowerShell.

intermediate

What information do you need to authenticate an application using a service principal?

You need the service principal's Application (client) ID, Tenant ID, and a secret (password) or certificate to authenticate.

intermediate

How can you limit the permissions of a service principal?

Assign only the necessary roles and scopes to the service principal using Azure Role-Based Access Control (RBAC). This follows the principle of least privilege.

What does a service principal represent in Azure?

A An identity for an application

B A user account for a person

C A virtual machine

D A storage account

A service principal is an identity created for an application to access Azure resources securely.

Which of these is NOT needed to authenticate with a service principal?

A Client ID

B Tenant ID

C Client secret or certificate

D User password

User passwords are not used; authentication uses client ID, tenant ID, and secret or certificate.

How do you restrict what a service principal can do?

A By changing the user password

B By deleting it

C By assigning roles with limited permissions

D By moving it to another subscription

Assigning roles with limited permissions controls what the service principal can access.

Which tool can you use to create a service principal?

A Microsoft Word

B Azure CLI

C Windows Explorer

D Excel

Azure CLI is a command-line tool to create and manage service principals.

Why is using a service principal better than using a user account for app access?

A It improves security and automation

B It requires a password change every day

C It costs more

D It uses less memory

Service principals improve security by avoiding personal credentials and support automation.

Explain what a service principal is and why it is important for applications in Azure.

Think about how apps need their own login to access cloud resources safely.

Describe the steps and information needed to create and use a service principal for an application.

Consider the process from app registration to permission assignment.

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