Skip to content

Commit fc51038

Browse files
author
Simonx Xu
authored
Merge pull request #8193 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main)
2 parents 44fdbe8 + 93330b1 commit fc51038

File tree

2 files changed

+14
-4
lines changed

2 files changed

+14
-4
lines changed

support/azure/virtual-machines/windows/unexpected-vm-reboot-root-cause-analysis.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ services: virtual-machines
55
ms.service: azure-virtual-machines
66
ms.workload: infrastructure-services
77
ms.topic: how-to
8-
ms.date: 11/17/2023
9-
ms.reviewer: tagangwa, macla, v-weizhu
8+
ms.date: 02/11/2025
9+
ms.reviewer: tagangwa, macla, sinhamanisha, v-weizhu
1010
ms.custom: sap:VM restarted or stopped unexpectedly
1111
---
1212
# How to check Root Cause Analysis of unexpected Azure virtual machine reboots
@@ -17,6 +17,8 @@ Azure provides methods to access detailed Root Cause Analysis (RCA) of unexpecte
1717

1818
## Method 1: Check resource health
1919

20+
Azure Resource Health monitors the health of Azure resources and provides insights for troubleshooting. In cloud environments where direct access to servers or infrastructure is impossible, Resource Health is important to reduce troubleshooting efforts. Its main purpose is to help quickly identify if the root cause of a problem is within your application or due to an event within the Azure platform, thus making issue resolution more efficient and minimizing downtime. To understand the cause of an unexpected VM reboot scenario using Resource Health, follow these steps:
21+
2022
1. Navigate to the impacted VM in the Azure portal.
2123
2. Go to the **Help** section and then select **Resource health**.
2224
3. Check the health events for the unexpected VM reboot to get RCA information.

support/power-platform/power-apps/manage-apps/wrap-issues.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Troubleshoot wrap issues in Power Apps
33
description: Provides resolutions for issues related to the wrap feature in Power Apps.
4-
ms.reviewer: sitaramp
4+
ms.reviewer: sitaramp, koagarwa
55
ms.author: arijitba
66
author: arijitba
7-
ms.date: 03/04/2024
7+
ms.date: 02/11/2025
88
ms.custom: has-azure-ad-ps-ref, azure-ad-ref-level-one-done, sap:App Management\Wrap an app
99
---
1010
# Troubleshoot issues with the wrap feature in Power Apps
@@ -238,6 +238,14 @@ The following Azure key vault errors might appear in wrap for Power Apps and can
238238

239239
:::image type="content" source="media/wrap-issues/provisioning-profile-secret-tag.png" alt-text="Screenshot that shows how to create a tag for iOS Provisioning Profile Secret." lightbox="media/wrap-issues/provisioning-profile-secret-tag.png":::
240240

241+
## Issue 7 - Wrap app sign-in fails
242+
243+
1. Verify if the user has access to the application. For more information, see [Share a canvas app with your organization](/power-apps/maker/canvas-apps/share-app).
244+
245+
2. If the user has access permissions, [review the app's Conditional Access policies in the Microsoft Entra admin center](/entra/identity/monitoring-health/how-to-view-applied-conditional-access-policies?tabs=microsoft-entra-admin-center#how-to-view-conditional-access-policies). Ensure you have a role that allows you to see both the sign-in logs and the Conditional Access policies.
246+
247+
3. To explore the results and troubleshoot sign-in errors, copy the correlation ID from the mobile screen showing the failed sign-in and follow the guide in [How to troubleshoot Microsoft Entra sign-in errors](/entra/identity/monitoring-health/howto-troubleshoot-sign-in-errors).
248+
241249
## Other issues in wrap for Power Apps
242250

243251
For all other issues, or if your issue persists after following these steps, see [Next steps](#next-steps) later in this article to report the issue through a support request. You need to provide a repro video, screenshots, or both, and a session ID that can be get in the following ways:

0 commit comments

Comments
 (0)