Skip to content

Commit cc51b4b

Browse files
authored
Merge pull request #8645 from MicrosoftDocs/main
Auto push to live 2025-04-03 02:00:02
2 parents 198bc77 + 6dc8670 commit cc51b4b

File tree

62 files changed

+731
-136
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

62 files changed

+731
-136
lines changed

support/azure/.openpublishing.redirection.azure.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6307,6 +6307,10 @@
63076307
{
63086308
"source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",
63096309
"redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"
6310+
},
6311+
{
6312+
"source_path": "azure-kubernetes/create-upgrade-delete/akscapacityerror.md",
6313+
"redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/akscapacityheavyusage-error"
63106314
}
63116315
]
63126316
}

support/azure/azure-kubernetes/create-upgrade-delete/akscapacityerror.md renamed to support/azure/azure-kubernetes/error-codes/akscapacityheavyusage-error.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Troubleshoot the AKSCapacityError error code
3-
description: Discusses how to troubleshoot the AKSCapacityError error when you create or start a Kubernetes cluster.
2+
title: Troubleshoot the AksCapacityHeavyUsage error code
3+
description: Discusses how to troubleshoot the AksCapacityHeavyUsage error when you create or start a Kubernetes cluster.
44
ms.date: 05/29/2024
55
author: axelgMS
66
ms.author: axelg
@@ -56,6 +56,6 @@ Capacity is often reclaimed when other users stop or delete their AKS clusters.
5656

5757
For more information about improvements that we're making toward delivering a resilient cloud supply chain, see [this September 2021 Azure Blog article](https://azure.microsoft.com/blog/advancing-reliability-through-a-resilient-cloud-supply-chain/).
5858

59-
- [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
59+
- [General troubleshooting of AKS cluster creation issues](../create-upgrade-delete/troubleshoot-aks-cluster-creation-issues.md)
6060

6161
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -368,3 +368,5 @@
368368
href: error-codes/vmextensionerror-vhdfilenotfound.md
369369
- name: UnsatisfiablePDB error
370370
href: error-codes/unsatisfiablepdb-error.md
371+
- name: AksCapacityHeavyUsage error
372+
href: error-codes/akscapacityheavyusage-error.md

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-managed-identities.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Azure File Sync managed identity issues
33
description: Troubleshoot common issues when your Azure File Sync deployment is configured to use managed identities.
44
ms.service: azure-file-storage
55
ms.topic: troubleshooting
6-
ms.date: 11/04/2024
6+
ms.date: 04/02/2025
77
author: khdownie
88
ms.author: kendownie
99
---
@@ -32,13 +32,13 @@ Get-AzStorageSyncServer -ResourceGroupName <string> -StorageSyncServiceName <str
3232
Verify the `ApplicationId` property has a GUID which indicates that the server is configured to use a system-assigned managed identity. Once the server uses a system-assigned managed identity, the value of the `ActiveAuthType` property is updated to `ManagedIdentity`. If the value is `Certificate`, the server uses shared keys to authenticate to Azure file shares.
3333

3434
> [!NOTE]
35-
> Once a server is configured to use a system-assigned managed identity, it can take up to one hour before the server uses the system-assigned managed identity to authenticate to the Storage Sync Service and Azure file shares.
35+
> Once a server is configured to use a system-assigned managed identity, it can take up to 15 minutes before the server uses the system-assigned managed identity to authenticate to the Storage Sync Service and Azure file shares.
3636
3737
## Set-AzStorageSyncServiceIdentity cmdlet doesn't configure a server to use a system-assigned managed identity
3838

3939
If running the `Set-AzStorageSyncServiceIdentity` cmdlet doesn't configure a registered server to use a system-assigned managed identity, it's likely because the server doesn't have a system-assigned managed identity.
4040

41-
To enable a system-assigned managed identity on a registered server that has the Azure File Sync v19 agent installed, perform the following steps:
41+
To enable a system-assigned managed identity on a registered server that has the Azure File Sync v20 agent installed, perform the following steps:
4242

4343
- If the server is hosted outside of Azure, it must be an Azure Arc-enabled server to have a system-assigned managed identity. For more information about Azure Arc-enabled servers and how to install the Azure Connected Machine agent, see [Azure Arc-enabled servers Overview](/azure/azure-arc/servers/overview).
4444

support/azure/virtual-machines/windows/windows-11-support-azure-virtual-machines.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.custom: sap:VM Admin - Windows (Guest OS)
88
ms.reviewer: scotro, kageorge, jarrettr, yutorigo, v-leedennis
99
editor: v-jsitser
1010
ms.topic: upgrade-and-migration-article
11-
ms.date: 01/08/2025
11+
ms.date: 04/02/2025
1212
---
1313
# Windows 11 support on Azure virtual machines
1414

@@ -108,11 +108,11 @@ The following sections provide more detail about the three main criteria: VM gen
108108

109109
### VM generation
110110

111-
VMs must be generation 2. You can't upgrade generation 1 VMs to generation 2.
111+
VMs must be generation 2. You can upgrade VMs from Generation 1 to Generation 2 by [upgrading to the Trusted launch security type](/azure/virtual-machines/trusted-launch-existing-vm-gen-1).
112112

113113
### Trusted launch
114114

115-
VMs must be enabled for trusted launch together with secure boot and virtual TPM. Upgrading VMs from standard security to trusted launch isn't supported. Many VMs are affected by this requirement. This is because before [June 28, 2023](https://techcommunity.microsoft.com/t5/azure-confidential-computing/announcing-trusted-launch-as-default-in-azure-portal/ba-p/3854872), trusted launch wasn't the default security type option when you created a VM in the Azure portal. Also, when Windows 11 was released, trusted launch wasn't available as a feature in Windows Azure.
115+
VMs must be enabled for Trusted launch together with secure boot and virtual TPM. [Upgrading VMs from standard security to Trusted launch](/azure/virtual-machines/trusted-launch-existing-vm-gen-1) is supported. Many VMs are affected by this requirement. This is because before [June 28, 2023](https://techcommunity.microsoft.com/t5/azure-confidential-computing/announcing-trusted-launch-as-default-in-azure-portal/ba-p/3854872), trusted launch wasn't the default security type option when you created a VM in the Azure portal. Also, when Windows 11 was released, trusted launch wasn't available as a feature in Windows Azure.
116116

117117
### CPU
118118

support/entra/entra-id/toc.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -279,6 +279,15 @@
279279
href: app-integration/404-not-found-error-manage-objects-microsoft-graph.md
280280
- name: Use managed identities to call Graph APIs in VB.Net and C#
281281
href: users-groups-entra-apis/call-graph-api-using-managed-dentities.md
282+
- name: The memberOf API returns null values for properties
283+
href: users-groups-entra-apis/memberof-api-returns-null-properties.md
284+
- name: Getting access denied errors (Authorization)
285+
items:
286+
- name: Error "The identity of the calling application could not be established"
287+
href: users-groups-entra-apis/identity-of-calling-application-not-established.md
288+
- name: Add an owner to an application
289+
href: users-groups-entra-apis/add-owner-for-application-microsoft-graph.md
290+
282291
- name: Microsoft Entra User Provisioning and Synchronization
283292
items:
284293
- name: User Sign-in or password Problems
Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
---
2+
title: Add an Owner to an Application Using Microsoft Graph
3+
description: Introduces how to add an owner (service principle) to an application using Microsoft Graph.
4+
ms.date: 04/03/2025
5+
ms.reviewer: willfid, v-weizhu
6+
ms.service: entra-id
7+
ms.custom: sap:Getting access denied errors (Authorization)
8+
---
9+
# Add an owner to an application using Microsoft Graph
10+
11+
When an application is authenticated, you might want to be able to update its own properties such as the client secret or certificate. To do so, the application must be an owner of itself. You can implement this using the [Microsoft Graph API - Add owner](/graph/api/application-post-owners).
12+
13+
This article outlines the required permission and step-by-step instructions to add a service principal associated with an application as an owner of the application using Microsoft Graph.
14+
15+
## Required permission
16+
17+
The least privileged permissions for adding an owner to an application are described in the [Add owner - Permissions](/graph/api/application-post-owners#permissions) table. These permissions, such as `Application.ReadWrite.OwnedBy`, allow an application to manage applications of which it is an owner.
18+
19+
## Add an owner
20+
21+
Application owners can be individual users, the associated service principal, or another service principal. The following sections describe how to add the related service principal to an application as an owner.
22+
23+
### Step 1: Get the application's Object ID
24+
25+
To get the **Object ID** of the application you want to add an owner to, follow these steps:
26+
27+
1. Sign in to the [Azure portal](https://portal.azure.com).
28+
2. Navigate to the Microsoft Entra admin center.
29+
3. Browse to **Identity** > **Applications** > **App registrations**.
30+
4. Locate the application and copy its **Object ID**.
31+
32+
:::image type="content" source="media/add-owner-for-application-microsoft-graph/application-object-id.png" alt-text="Screenshot that shows an application's Object ID.":::
33+
34+
### Step 2: Get the owner (service principal's Object ID)
35+
36+
To get the **Object ID** of the service principal associated with the application, follow these steps:
37+
38+
1. Sign in to the [Azure portal](https://portal.azure.com).
39+
2. Navigate to the Microsoft Entra admin center.
40+
3. Browse to **Identity** > **Applications** > **Enterprise registrations**.
41+
4. Locate the application and copy its **Object ID**.
42+
43+
:::image type="content" source="media/add-owner-for-application-microsoft-graph/service-principle-object-id.png" alt-text="Screenshot that shows an service principal's Object ID.":::
44+
45+
### Step 3: Add the owner to the application
46+
47+
Here're two methods to do this:
48+
49+
- [Method 1: Using Microsoft Graph Explorer](#method-1-using-microsoft-graph-explorer)
50+
- [Method 2: Using Microsoft Graph PowerShell](#method-2-using-microsoft-graph-powershell)
51+
52+
#### Method 1: Using Microsoft Graph Explorer
53+
54+
1. Navigate to [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
55+
2. Sign in with a user account that has the necessary permissions to update application owners, such as a Global Administrator or Application Administrator.
56+
3. Use the following request:
57+
58+
```msgraph-interactive
59+
POST https://graph.microsoft.com/v1.0/applications/{application-object-id}/owners/$ref
60+
61+
Content-Type: application/json
62+
63+
{
64+
"@odata.id": "https://graph.microsoft.com/v1.0/directoryObjects/{service-principal-id}"
65+
}
66+
```
67+
68+
> [!NOTE]
69+
> Replace `{application-object-id}` with the **Object ID** of your application and `{service-principal-id}` with the **Object ID** of the service principal.
70+
71+
Here's an example of what it looks like in Microsoft Graph Explorer:
72+
73+
:::image type="content" source="media/add-owner-for-application-microsoft-graph/microsoft-graph-api-call.png" alt-text="Screenshot that shows a request in Microsoft Graph Explorer." lightbox="media/add-owner-for-application-microsoft-graph/microsoft-graph-api-call.png":::
74+
75+
76+
##### Troubleshoot Forbidden (403) error
77+
78+
You might encounter the following error during this process:
79+
80+
```output
81+
"error": {
82+
"code": "Authorization_RequestDenied",
83+
"message": "Insufficient privileges to complete the operation.",
84+
"innerError": {
85+
"date": "2021-12-09T17:41:54",
86+
"request-id": "b1909fc0-aa5c-4b43-8a1f-xxxxxxxxxxxx",
87+
"client-request-id": "836e08bb-a12d-4ade-c761-xxxxxxxxxxxx"
88+
}
89+
}
90+
```
91+
92+
To resolve the issue, consent to the API permission **Application.ReadWrite.All** for Microsoft Graph Explorer under the **Modify permissions** tab.
93+
94+
:::image type="content" source="media/add-owner-for-application-microsoft-graph/modify-permissions.png" alt-text="Screenshot that shows how to modify permission in Microsoft Graph Explorer." lightbox="media/add-owner-for-application-microsoft-graph/modify-permissions.png":::
95+
96+
#### Method 2: Using Microsoft Graph PowerShell
97+
98+
Here's an example of Microsoft Graph PowerShell scripts to add an owner to an application:
99+
100+
```powershell
101+
Connect-MgGraph -Scopes Application.ReadWrite.All
102+
103+
# Owner
104+
$OwnerServicePrincipalObjectId = "96858eb3-xxxx-xxxx-xxxx-33a6b0dc2430"
105+
106+
# Application to add owner to
107+
$ApplicationObjectId = "b7463aa1-xxxx-xxxx-xxxx-0963d6c00485"
108+
109+
$Owner = @{
110+
"@odata.id" = "https://graph.microsoft.com/v1.0/directoryObjects/$($OwnerServicePrincipalObjectId)"
111+
}
112+
113+
New-MgApplicationOwnerByRef -ApplicationId $ApplicationObjectId -BodyParameter $Owner
114+
```
115+
116+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: The Identity of the Calling Application Could Not Be Established
3+
description: Provides solutions to the identity of the calling application could not be established error when using Microsoft Graph.
4+
ms.date: 04/03/2025
5+
ms.service: entra-id
6+
ms.custom: sap:Getting access denied errors (Authorization)
7+
ms.reviewer: willfid, v-weizhu
8+
---
9+
# Error "The identity of the calling application could not be established"
10+
11+
This article provides solutions to the error message "The identity of the calling application could not be established" when using Microsoft Graph.
12+
13+
## Symptoms
14+
15+
When using Microsoft Graph or some services that rely on it, you encounter the following error message:
16+
17+
> The identity of the calling application could not be established
18+
19+
## Cause
20+
21+
This error occurs because the `oid` and `sub` claims are missing from the access token. The root cause is that the service principal doesn't exist in the tenant or the tenant isn't aware of the application.
22+
23+
## Solution
24+
25+
To resolve this error, add the service principal to the tenant and consent to the permissions required by the application.
26+
27+
You can [build an admin consent URL](/entra/identity/enterprise-apps/grant-admin-consent#construct-the-url-for-granting-tenant-wide-admin-consent) like the following one:
28+
29+
`https://login.microsoftonline.com/{organization}/adminconsent?client_id={client-id}`
30+
31+
Then, sign in with a Global Administrator account of the tenant where you are trying to access resources.
32+
33+
> [!NOTE]
34+
> - Replace `{organization}` with the tenant ID, for example, aaaaaaaaaaaa-bbbb-cccc-1111-22222222.
35+
> - Replace `{client-id}` with the application ID, for example, dddddddddddd-eeee-ffff-3333-44444444.
36+
37+
## References
38+
39+
- [Understanding Microsoft Entra application consent experiences](/entra/identity-platform/application-consent-experience)
40+
- [Overview of permissions and consent in the Microsoft identity platform](/entra/identity-platform/permissions-consent-overview)
41+
- [Retire Service Principal-Less Authentication](/entra/identity-platform/retire-service-principal-less-authentication)
42+
43+
44+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
27.8 KB
Loading
34.4 KB
Loading

0 commit comments

Comments
 (0)