Skip to content

Commit 81adb25

Browse files
authored
Updates from editor
1 parent f3653f7 commit 81adb25

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed
Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
title: IDX14102 Error When Using Microsoft Graph PowerShell
3-
description: Describes an error that occurs when you run the Microsoft Graph PowerShell Connect-MgGraph cmdlet and provides solutions to it.
4-
ms.date: 06/18/2025
3+
description: Resolves an error that occurs when you run the Microsoft Graph PowerShell cmdlet Connect-MgGraph.
4+
ms.date: 06/30/2025
55
ms.service: entra-id
66
ms.custom: sap:Problem with using the Graph SDK - libraries
77
ms.reviewer: adoyle, willfid, nualex, v-weizhu
88
---
99

1010
# Microsoft Graph PowerShell throws error "IDX14102: Unable to decode the header"
1111

12-
This article provides solutions to an error "IDX14102: Unable to decode the header" that occurs when you use Microsoft Graph PowerShell.
12+
This article provides solutions to the error "IDX14102: Unable to decode the header" that occurs when you use Microsoft Graph PowerShell.
1313

1414
## Symptoms
1515

@@ -19,7 +19,7 @@ When running the Microsoft Graph PowerShell command `Connect-MgGraph -AccessToke
1919
2020
## Cause
2121

22-
This error occurs because an invalid access token is passed to the `AccessToken` parameter of the `Connect-MgGraph` cmdlet. This problem often occurs when the token is acquired via Azure PowerShell's `Get-AzAccessToken` cmdlet and passed as a `SecureString`. This behavior is observed starting with version 5.0.0 of the `Az.Accounts` module. Starting from Microsoft Graph PowerShell version 2.28.0, the `Connect-MgGraph` command only accepts a plaint string for the `AccessToken` parameter.
22+
This error occurs because an invalid access token is passed to the `AccessToken` parameter of the `Connect-MgGraph` cmdlet. This problem often occurs when the token is obtained via Azure PowerShell's `Get-AzAccessToken` cmdlet and passed as a `SecureString`. This behavior is observed starting with version 5.0.0 of the `Az.Accounts` module. Starting from Microsoft Graph PowerShell version 2.28.0, the `Connect-MgGraph` command accepts only a plain string as the `AccessToken` parameter.
2323

2424
## Solution
2525

@@ -29,9 +29,9 @@ Here are two solutions for resolving this issue:
2929

3030
For more information about access tokens, see [Access tokens in the Microsoft identity platform](/entra/identity-platform/access-tokens).
3131

32-
- If you use the `Get-AzAccessToken` cmdlet to acquire the access token, use one of the following methods:
32+
- If you use the `Get-AzAccessToken` cmdlet to obtain the access token, use one of the following methods:
3333

34-
- Downgrade `Az.Accounts` to version 4.2.0, to avoid the token being returned as a `SecureString`.
34+
- Downgrade `Az.Accounts` to version 4.2.0 to avoid the token being returned as a `SecureString`.
3535
- Convert the token from `SecureString` to `String`:
3636

3737
```azurepowershell
@@ -40,4 +40,4 @@ Here are two solutions for resolving this issue:
4040
Connect-MgGraph -AccessToken (ConvertFrom-SecureString -SecureString $microsoftGraphToken.Token -AsPlainText)
4141
```
4242
43-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
43+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

0 commit comments

Comments
 (0)