Merge pull request #327 from msewaweru/freshness-troubleshooting

Freshness pass for the troubleshooting article

Author: timayabi2020

microsoftgraph/docs-conceptual/get-started.md

@@ -158,5 +158,6 @@ Disconnect-MgGraph
 
 ## Next steps
 
-- [Learn how to navigate the SDK](navigating.md)
-- [Use app-only authentication with the Microsoft Graph PowerShell SDK](app-only.md)
+- Work around the [Unverified publisher known issue](troubleshooting.md#unverified-publisher-known-issue).
+- [Learn how to navigate the SDK](navigating.md).
+- [Use app-only authentication with the Microsoft Graph PowerShell SDK](app-only.md).

microsoftgraph/docs-conceptual/images/sample-debug-response.png

@@ -3,11 +3,11 @@ title: "Error handling and troubleshooting cmdlets"
 description: "Learn how to diagnose common errors in Microsoft Graph PowerShell"
 
 ms.topic: troubleshooting
-ms.date: 05/22/2023
+ms.date: 08/08/2023
 ms.author: eunicewaweru
 manager: CelesteDG
 author: msewaweru
-reviewer: maisarissi,peombwa
+reviewer: carolkigoonya,peombwa
 ---
 
 # Troubleshooting common errors in Microsoft Graph PowerShell
@@ -58,6 +58,16 @@ Alternatively, use [New-MgServicePrincipalAppRoleAssignment](/powershell/module/
 
 For more info, see [App-only authentication](app-only.md).
 
+## Unverified publisher known issue
+
+`Unverified publisher` error message occurs during Microsoft Graph PowerShell app consent.
+
+To remove this error, you can use an app registration of your own, on which you can set yourself as the verified publisher. You'll need to go through the [publisher verification process](/azure/active-directory/develop/publisher-verification-overview), and use the app registration to consent to the permissions required by Microsoft Graph PowerShell, as shown below:
+
+```powershell
+Connect-MgGraph -AppId "{your-own-app-id}" -Scopes "scope"
+```
+
 ## Using -Debug
 
 The **-Debug** parameter provides a powerful way to examine a script while it's running in order to identify and correct errors in the script. The following are the important parts of a **-Debug** output: