You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Troubleshoot common issues when your Azure File Sync deployment is configured to use managed identities.
4
4
ms.service: azure-file-storage
5
5
ms.topic: troubleshooting
6
-
ms.date: 06/05/2025
6
+
ms.date: 06/09/2025
7
7
author: khdownie
8
8
ms.author: kendownie
9
9
---
@@ -65,27 +65,32 @@ When you try to delete a Storage Sync Service, you might get the following error
65
65
66
66
This issue occurs when your file share has unused Azure File Sync snapshots. To reduce your cost, the unused snapshots are deleted before removing the Storage Sync Service. The snapshot count varies with the dataset size. If you can't delete the Storage Sync Service after a few hours, try again the next day.
67
67
68
-
## Error "Failed to perform resource identity operation" when creating Storage Sync Service
68
+
## Error "Failed to perform resource identity operation" when creating a Storage Sync Service
69
69
70
-
When creating a Storage Sync Service, you might get the following error: "Failed to perform resource identity operation." This error occurs when you delete a Storage Sync Service and then attempt to recreate it using the same name within the same tenant.
70
+
When creating a Storage Sync Service, you might get the following error:
71
71
72
-
To resolve this issue, you can create a new name for the Storage Sync Service, investigate the conflicting app in Microsoft Entra ID (and delete it manually if needed), or wait for the system to auto-clean up the app.
72
+
> Failed to perform resource identity operation.
73
73
74
-
-**Use a different Storage Sync Service name**
75
-
Create the Storage Sync Service with a different name than the one previously used.
74
+
This issue occurs in one of the following scenarios:
76
75
77
-
-**How to investigate the conflicting service principal in Microsoft Entra ID**
78
-
A conflicting service principal app might still exist in Microsoft Entra ID (formerly Azure AD). This app was likely created during the initial provisioning of the Storage Sync Service.
76
+
- You delete a Storage Sync Service and then try to recreate it using the same name within the same tenant.
79
77
80
-
-**Choose manual deletion (optional)**
81
-
If you need immediate resolution, you can manually delete the conflicting app:
82
-
1. Go to the Microsoft Entra admin center.
83
-
1. Navigate to **Enterprise applications**.
84
-
1. Search for the app name that matches the Storage Sync Service.
85
-
1. Select the app and then select **Delete**.
78
+
- A conflicting service principal app might still exist in Microsoft Entra ID.
86
79
87
-
-**Wait for automatic cleanup**
88
-
If the app was created by the Storage Sync Service provisioning process, the system will automatically delete it within 24 hours. If the service isn't urgently needed, you may choose to wait for this automatic cleanup to complete.
80
+
This app was likely created during the initial provisioning of the Storage Sync Service and will be deleted automatically within 24 hours.
81
+
82
+
To resolve this issue, use one of the following methods:
83
+
84
+
- Create the Storage Sync Service with a different name than the one previously used.
85
+
86
+
- Wait for the automatic cleanup of the conflicting service principal app to finish, or delete it manually.
87
+
88
+
If the service isn't urgently required, wait for this automatic cleanup to finish. If an immediate resolution is needed, you can manually delete the conflicting app:
89
+
90
+
1. Go to the Microsoft Entra admin center.
91
+
2. Navigate to **Enterprise applications**.
92
+
3. Search for the app name that matches the Storage Sync Service.
93
+
4. Select the app and then select **Delete**.
89
94
90
95
## Permissions required to access a storage account and Azure file share
description: Provides solutions for common errors you might experience when subscribing to Azure Native Integrations in Azure Marketplace.
4
+
author: ProfessorKendrick
5
+
ms.author: kkendrick
6
+
ms.service: partner-services
7
+
ms.topic: error-reference #Don't change
8
+
ms.date: 05/29/2025
9
+
#customer intent: As a customer, I want troubleshoot errors so that I can subscribe to an Azure Native Integrations partner service.
10
+
---
11
+
12
+
# Azure Native Integration purchase errors
13
+
14
+
This article describes error messages you may encounter when subscribing to an Azure Native Integrations partner service in Azure Marketplace and provides solutions to help you resolve those errors.
15
+
16
+
|Error message |Details |
17
+
|---------|---------|
18
+
|"The Microsoft.SaaS RP is not registered on the Azure subscription." |Before you can use a resource provider, you must make sure that your Azure subscription is registered for it. For more information, see [Register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) and [Resolve errors for resource provider registration](/azure/azure-resource-manager/troubleshooting/error-register-resource-provider). |
19
+
|"Plan cannot be purchased on a free subscription, please upgrade your account." |You can't make Azure Marketplace purchases on a free Azure subscription. For more information, see the [Azure free account FAQ](https://azure.microsoft.com/free/free-account-faq) and [Purchase a SaaS offer in the Azure portal](/marketplace/purchase-saas-offer-in-azure-portal#common-error-messages-and-solutions). |
20
+
|"Purchase has failed because we couldn't find a valid payment method associated with your Azure subscription." |Use a different Azure subscription, or add or update credit card or payment method information for this subscription. For more information, see [Purchase a SaaS offer in the Azure portal](/marketplace/purchase-saas-offer-in-azure-portal#common-error-messages-and-solutions). |
21
+
|"The Publisher does not make available Offer, Plan in your Subscription/Azure account's region." |The offer or the specific plan isn't available to the billing account market that's connected to the Azure subscription. |
22
+
|"Enrollment for Azure Marketplace is set to Free/BYOL SKUs only, purchase for Azure product is not allowed. Please contact your enrollment administrator to change EA settings." |Enterprise administrators can disable or enable Azure Marketplace purchases for all Azure subscriptions that are under their enrollment. For more information, see [Enabling Azure Marketplace purchases](/azure/cost-management-billing/manage/ea-azure-marketplace#enabling-azure-marketplace-purchases) and [Introduction to listing options](/partner-center/marketplace/determine-your-listing-type#overview). |
23
+
|"Marketplace is not enabled for the Azure subscription." |Enterprise administrators can disable or enable Azure Marketplace purchases for all Azure subscriptions that are under their enrollment. For more information, see [Enabling Azure Marketplace purchases](/azure/cost-management-billing/manage/ea-azure-marketplace#enabling-azure-marketplace-purchases). |
24
+
|"Plan by publisher is not available to you for purchase due to private marketplace settings made by your tenant's IT administrator." |The customer uses a private marketplace to limit the access of its organization to specific offers and plans. The specific offer or plan wasn't set up to be available in the tenant's private marketplace. Contact your tenant's IT administrator. |
25
+
|"The EA subscription doesn't allow Marketplace purchases." |Use a different subscription or check whether your Enterprise Agreement subscription is enabled for Azure Marketplace purchases. For more information, see [Enabling Azure Marketplace purchases](/azure/cost-management-billing/manage/ea-azure-marketplace#enabling-azure-marketplace-purchases). |
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/how-to-use-perfInsights-linux.md
+26-11Lines changed: 26 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,22 +12,37 @@ ms.collection: linux
12
12
ms.workload: infrastructure-services
13
13
ms.tgt_pltfrm: vm-linux
14
14
ms.topic: troubleshooting
15
-
ms.date: 05/02/2025
15
+
ms.date: 06/10/2025
16
16
ms.author: genli
17
17
---
18
18
# Troubleshoot Linux virtual machine performance issues with Performance Diagnostics (PerfInsights)
19
19
20
20
**Applies to:**:heavy_check_mark: Linux VMs
21
21
22
-
[PerfInsights Linux](https://aka.ms/perfinsightslinuxdownload) is a self-help diagnostics tool that collects and analyzes the diagnostic data, and provides a report to help troubleshoot Linux virtual machine performance problems in Azure. PerfInsights can be run on supported virtual machines as a standalone tool, or directly from the portal by using [Performance Diagnostics for Azure virtual machines](../windows/performance-diagnostics.md).
22
+
[PerfInsights Linux](https://aka.ms/perfinsightslinuxdownload) is a self-help diagnostics tool that collects and analyzes the diagnostic data, and provides a report to help troubleshoot Linux virtual machine performance problems in Azure. Use Performance Diagnostics to identify and troubleshoot performance issues in one of two modes:
23
23
24
-
If you are experiencing performance problems with virtual machines, before contacting support, run this tool.
24
+
-**Continuous diagnostics** collects data at five-second intervals and reports actionable insights about high resource usage every five minutes.
25
25
26
-
> [!NOTE]
27
-
> [Continuous diagnostics](../windows/performance-diagnostics.md) is currently supported only on Windows.
26
+
-**On-demand diagnostics** helps you troubleshoot an ongoing performance issue with more in-depth data, insights, and recommendations based on data collected at a single point in time.
27
+
28
+
This article explains how to download the Performance Diagnostics extension to your Linux VM and run the tool using the CLI tool. You can also [run Performance Diagnostics from the portal](../windows/performance-diagnostics.md).
29
+
30
+
If you are experiencing performance problems with virtual machines, before contacting support, run this tool.
28
31
29
32
## Supported troubleshooting scenarios
30
33
34
+
You can use Performance Diagnostics to troubleshoot various scenarios. The following sections describe common scenarios for using Continuous and On-Demand Performance Diagnostics to identify and troubleshoot performance issues. For a comparison of Continuous and On-Demand Performance Diagnostics, see [Performance Diagnostics insights and reports](../windows/performance-diagnostics.md).
35
+
36
+
## Continuous diagnostics
37
+
38
+
Continuous Performance diagnostics lets you identify high resource usage by monitoring your VM regularly for:
39
+
40
+
- High CPU usage: Detects high CPU usage periods and shows the top CPU usage consumers during those periods.
41
+
42
+
- High memory usage: Detects high memory usage periods and shows the top memory usage consumers during those periods.
43
+
44
+
- High disk usage: Detects high disk usage periods on physical disks and shows the top disk usage consumers during those periods.
45
+
31
46
PerfInsights can collect and analyze several kinds of information. The following sections cover common scenarios.
32
47
33
48
### Quick performance analysis
@@ -44,7 +59,7 @@ This scenario collects basic information such as storage and hardware configurat
>[`*`] Please refer to [Known issues](#known-issues) section
@@ -250,27 +265,27 @@ To run the PerfInsights tool, follow these steps:
250
265
sudo python perfinsights.py
251
266
```
252
267
253
-
:::image type="content" source="media/how-to-use-perfinsights-linux/perfinsights-linux-commandline.png" alt-text="Screenshot of PerfInsights Linux command-line output.":::
268
+
:::image type="content" source="media/how-to-use-perfinsights-linux/perfinsights-linux-command-line.png" alt-text="Screenshot of PerfInsights Linux command-line output." lightbox="media/how-to-use-perfinsights-linux/perfinsights-linux-command-line.png":::
254
269
255
270
The basic syntax for running PerfInsights scenarios is:
0 commit comments