Skip to content

Commit 12b4e77

Browse files
Merge pull request #313443 from MicrosoftDocs/main
Auto Publish – main to live - 2026-03-20 06:00 UTC
2 parents e693dd2 + 1ec4afd commit 12b4e77

58 files changed

Lines changed: 546 additions & 349 deletions

File tree

Some content is hidden

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

articles/azure-netapp-files/control-plane-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Monitoring, auditing, and logging are critical for maintaining security and comp
7676
- **Function:** Azure NetApp Files offers metrics on allocated storage, actual storage usage, volume I/OPS, and latency. These metrics help you understand usage patterns and volume performance. For more information, see [Metrics for Azure NetApp Files](azure-netapp-files-metrics.md).
7777
- **Use case:** Metrics are essential for performance tuning and capacity planning, allowing you to optimize your storage resources effectively.
7878
- **Azure Service Health:**
79-
- **Function:** Azure Service Health keeps you informed about the health of your Azure services, providing a personalized view of the status of your environment. For more information, see [Service Health portal classic experience overview](/azure/service-health/service-health-overview).
79+
- **Function:** Azure Service Health keeps you informed about the health of your Azure services, providing a personalized view of the status of your environment. For more information, see [Service Health portal classic experience overview](/azure/service-health/overview).
8080
- **Use case:** Azure Service Health helps you stay updated on planned maintenance and health advisories, ensuring minimal disruption to your operations.
8181
- **Audit logging:**
8282
- **Scope:** The control plane logs all PUT, POST, and DELETE API operations against Azure NetApp Files. These logs include actions such as creating snapshots, modifying volumes, and deleting resources. For more information, see [Are Azure activity logs supported in Azure NetApp Files?](faq-security.md#are-azure-activity-logs-supported-on-azure-netapp-files)

articles/azure-netapp-files/monitor-azure-netapp-files.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ For more information about Azure NetApp Files metrics, see [Metrics for Azure Ne
4141

4242
The [Azure Service Health dashboard](https://azure.microsoft.com/features/service-health) keeps you informed about the health of your environment. It provides a personalized view of the status of your Azure services in the regions where they are used. The dashboard provides upcoming planned maintenance and relevant health advisories while allowing you to manage service health alerts.
4343

44-
For more information, see [Azure Service Health dashboard](/azure/service-health/service-health-overview) documentation.
44+
For more information, see [Azure Service Health dashboard](/azure/service-health/overview) documentation.
4545

4646
## Capacity utilization monitoring
4747

articles/azure-resource-manager/templates/deploy-what-if.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -396,7 +396,7 @@ You see the expected changes and can confirm that you want the deployment to run
396396

397397
You can use the what-if operation through the Azure SDKs.
398398

399-
- For Python, use [what-if](/python/api/azure-mgmt-resource/azure.mgmt.resource.resources.v2019_10_01.operations.deploymentsoperations).
399+
- For Python, use [what-if](/python/api/azure-mgmt-resource-deployments/azure.mgmt.resource.deployments.models.deploymentwhatif).
400400
- For Java, use [DeploymentWhatIf Class](/java/api/com.azure.resourcemanager.resources.models.deploymentwhatif).
401401

402402
- For .NET, use [DeploymentWhatIf Class](/dotnet/api/microsoft.azure.management.resourcemanager.models.deploymentwhatif).

articles/azure-vmware/ecosystem-back-up-vms.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,4 +30,4 @@ You can find more information on these backup solutions here:
3030
- [Dell PPDM](https://www.dell.com/support/manuals/en-us/enterprise-copy-data-management/pp-dm_19.19_virtual_machines_ug/azure-vmware-solution-avs-on-microsoft-azure?guid=guid-600e65ba-95f3-4d7c-b8bb-4950abf2f9ad&lang=en-us)
3131
- [Rubrik](https://www.rubrik.com/en/products/cloud-data-management)
3232
- [Veeam](https://www.veeam.com/kb4012)
33-
- [Veritas](https://vrt.as/nb4avs)
33+
- [Veritas](https://www.veritas.com/support/en_US/doc/21902280-139625479-0/v19545363-139625479)

articles/azure-vmware/move-azure-vmware-solution-across-regions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Azure VMware Solution supports all backup solutions. You need CloudAdmin privile
8383

8484
- Restore VMs.
8585

86-
- Backup VM workload using [Veritas NetBackup solution](https://vrt.as/nb4avs).
86+
- Backup VM workload using [Veritas NetBackup solution](https://www.veritas.com/support/en_US/doc/21902280-139625479-0/v19545363-139625479).
8787

8888
>[!TIP]
8989
>You can use [Azure Resource Mover](../resource-mover/move-region-within-resource-group.md?toc=/azure/azure-resource-manager/management/toc.json) to verify and migrate the list of supported resources to move across regions, which are dependent on Azure VMware Solution.

articles/communication-services/concepts/troubleshooting-info.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ This article helps you troubleshoot issues that you might experience within your
2121

2222
You can view the health of your Azure Communication Services solution on the [Azure Service Health portal](https://portal.azure.com/#view/Microsoft_Azure_Health/AzureHealthBrowseBlade/%7E/serviceIssues). If you experience problems with your Azure Communication Services solution, check the Service Health portal first. Then you can determine whether there's a known issue with a resolution in progress before calling support or spending time troubleshooting.
2323

24-
[Azure Service Health portal](/azure/service-health/service-health-overview) provides a personalized view of the health of the Azure services and regions you're using. The Service Health portal is the best place to look for outages, planned maintenance activities, and other health advisories. Once you sign in, the authenticated Service Health experience knows which services and resources you currently use.
24+
[Azure Service Health portal](/azure/service-health/overview) provides a personalized view of the health of the Azure services and regions you're using. The Service Health portal is the best place to look for outages, planned maintenance activities, and other health advisories. Once you sign in, the authenticated Service Health experience knows which services and resources you currently use.
2525

26-
The best way to use Service Health is to set up [Service Health alerts](/azure/service-health/service-health-overview#configure-service-health-alerts) to notify you via your preferred communication channel. You receive notices for service issues, planned maintenance, or other changes that affect your Azure services and regions.
26+
The best way to use Service Health is to set up [Service Health alerts](/azure/service-health/overview#using-azure-service-health) to notify you via your preferred communication channel. You receive notices for service issues, planned maintenance, or other changes that affect your Azure services and regions.
2727

2828
If you're unable to sign in to your Service Health Portal, you can use the public facing **[Azure Status page](https://azure.status.microsoft)** to check for known issues. [Azure status overview](/azure/service-health/azure-status-overview) provides a global view of Azure services and regions from **[Azure status](https://azure.status.microsoft)**.
2929

0 commit comments

Comments
 (0)