Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-roles-oct2024

Author: rolyon

articles/api-center/configure-environments-deployments.md

@@ -73,9 +73,9 @@ Here you add a deployment by associating one of your APIs with the environment y
 
 1. In the left menu, under **Assets**, select **APIs**.
 
-1. Select an API, for example, the *Demo Conference API*.
+1. Select an API, for example, the *Conference API*.
 
-1. On the **Demo Conference API** page, under **Details**, select **Deployments** > **+ Add deployment**.
+1. On the **Conference API** page, under **Details**, select **Deployments** > **+ Add deployment**.
 
 1. In the **Add deployment** page, add the following information. If you previously defined the custom *Line of business* metadata or other metadata assigned to environments, you'll see them at the bottom of the page.
 
@@ -85,7 +85,7 @@ Here you add a deployment by associating one of your APIs with the environment y
     |**Identification**|After you enter the preceding title, Azure API Center generates this identifier, which you can override.| Azure resource name for the deployment.|
     | **Description** | Optionally enter a description. | Description of the deployment. |
     | **Environment** | Make a selection from the dropdown, such as *My Testing*, or optionally select **Create new**.| New or existing environment where the API version is deployed. |
-    | **Definition** | Select or add a definition file for a version of the Demo Conference API. | API definition file. |
+    | **Definition** | Select or add a definition file for a version of the Conference API. | API definition file. |
     | **Runtime URL** | Enter a base URL, for example, `https://api.contoso.com`. | Base runtime URL for the API in the environment.  |
     | **Line of business** | If you added this custom metadata, optionally make a selection from the dropdown, such as **IT**. | Custom metadata that identifies the business unit that manages APIs in the environment. |
 

articles/api-center/media/configure-environments-deployments/add-deployment.png

@@ -27,7 +27,7 @@ In this tutorial, you learn how to use the portal to:
 * One or more APIs that you want to register in your API center. Here are two examples, with links to their OpenAPI definitions:
 
     * [Swagger Petstore API](https://github.com/swagger-api/swagger-petstore/blob/master/src/main/resources/openapi.yaml)
-    * [Azure Demo Conference API](https://conferenceapi.azurewebsites.net?format=json)
+    * [Conference API](https://bigconference.azurewebsites.net)
 
 * Complete the previous tutorial, [Define custom metadata](add-metadata-properties.md), to define custom metadata for your APIs.
 
@@ -41,7 +41,7 @@ When you register (add) an API in your API center, the API registration includes
 
 After registering an API, you can add versions and definitions to the API.
 
-The following steps register two sample APIs: Swagger Petstore API and Demo Conference API (see [Prerequisites](#prerequisites)). If you prefer, register APIs of your own.
+The following steps register two sample APIs: Swagger Petstore API and Conference API (see [Prerequisites](#prerequisites)). If you prefer, register APIs of your own.
 
 1. In the [portal](https://portal.azure.com), navigate to your API center.
 
@@ -70,7 +70,7 @@ The following steps register two sample APIs: Swagger Petstore API and Demo Conf
 
 1. Select **Create**. The API is registered.
 
-1. Repeat the preceding three steps to register another API, such as the Demo Conference API.
+1. Repeat the preceding three steps to register another API, such as the Conference API.
 
 > [!TIP]
 > When you register an API in the portal, you can select any of the predefined API types or enter another type of your choice. 
@@ -89,9 +89,9 @@ Here you add a version to one of your APIs:
 
 1. In the portal, navigate to your API center.
 
-1. In the left menu, select **APIs**, and then select an API, for example, *Demo Conference API*.
+1. In the left menu, select **APIs**, and then select an API, for example, *Swagger Petstore*.
 
-1. On the Demo Conference API page, under **Details**, select **Versions** > **+ Add version**.
+1. On the API page, under **Details**, select **Versions** > **+ Add version**.
 
     :::image type="content" source="media/register-apis/add-version.png" alt-text="Screenshot of adding an API version in the portal." lightbox="media/register-apis/add-version.png":::
 
@@ -126,9 +126,9 @@ To add an API definition to your version:
         |**Title**| Enter a title of your choice, such as *v2 Definition*.|Name you choose for the API definition.|
         |**Identification**|After you enter the preceding title, Azure API Center generates this identifier, which you can override.| Azure resource name for the definition.|
         | **Description** | Optionally enter a description. | Description of the API definition. |
-        | **Specification name** | For the Demo Conference API, select **OpenAPI**. | Specification format for the API.|
-        | **Specification version** | Enter a version identifier of your choice, such as *2.0*. | Specification version. |
-        |**Document**        | Browse to a local definition file for the Demo Conference API, or enter a URL. Example URL: `https://conferenceapi.azurewebsites.net?format=json`   |  API definition file.     |
+        | **Specification name** | For the Petstore API, select **OpenAPI**. | Specification format for the API.|
+        | **Specification version** | Enter a version identifier of your choice, such as *3.0*. | Specification version. |
+        |**Document**        | Browse to a local definition file for the Petstore API, or enter a URL. Example URL: `https://raw.githubusercontent.com/swagger-api/swagger-petstore/refs/heads/master/src/main/resources/openapi.yaml`   |  API definition file.     |
 
         :::image type="content" source="media/register-apis/add-definition.png" alt-text="Screenshot of adding an API definition in the portal." lightbox="media/register-apis/add-definition.png" :::
 

articles/api-center/media/register-apis/add-definition.png

@@ -20,45 +20,28 @@ By using the `addProtocol` function, which registers a callback triggered before
 The first step is to add a reference to the protocol. The following example references the `pmtiles` library:
 
 ```html
-  <script src="https://unpkg.com/pmtiles@3.0.5/dist/pmtiles.js"></script>
+  <script src="https://unpkg.com/pmtiles@3.2.0/dist/pmtiles.js"></script>
 ```
 
 Next, initialize the MapLibre PMTiles protocol.
 
 ```js
-//Initialize the plugin.
-      const protocol = new pmtiles.Protocol();
-      atlas.addProtocol("pmtiles", (request) => {
-        return new Promise((resolve, reject) => {
-          const callback = (err, data) => {
-            if (err) {
-              reject(err);
-            } else {
-              resolve({ data });
-            }
-          };
-          protocol.tile(request, callback);
-        });
-      });
-```
-
-## Add PMTiles protocol
-
-To add the PMTiles protocol, hook the data source with the specified protocol URI scheme. The following sample uses the [Overture] building dataset to add building data over the basemap.
-
-```js
-const PMTILES_URL = "https://overturemaps-tiles-us-west-2-beta.s3.amazonaws.com/2024-07-22/buildings.pmtiles";
-protocol.add(new pmtiles.PMTiles(PMTILES_URL));
+  //Initialize the plugin.
+  const protocol = new pmtiles.Protocol();
+  atlas.addProtocol("pmtiles", protocol.tile);
 ```
 
 ## Add PMTiles as a map source
 
+The following sample uses the [Overture] building dataset to add building data over the basemap.
+
 PMTiles are added as a map source during the map event. Once added, the specified URI scheme is available to the Azure Maps Web SDK. In the following sample, the PMTiles URL is added as a `VectorTileSource`.
 
 ```js
+const PMTILES_URL = "https://overturemaps-tiles-us-west-2-beta.s3.amazonaws.com/2024-07-22/buildings.pmtiles";
 //Add the source to the map.
 map.sources.add(
-  new atlas.source.VectorTileSource("pmtiles", {
+  new atlas.source.VectorTileSource("my_source", {
     type: "vector",
     url: `pmtiles://${PMTILES_URL}`,
   })
@@ -77,7 +60,7 @@ The following sample uses the building theme's properties (for example, building
 ```js
 //Create a polygon extrusion layer.
 layer = new atlas.layer.PolygonExtrusionLayer(
-  "pmtiles",
+  "my_source",
   "building",
   {
     sourceLayer: "building",

articles/api-center/media/register-apis/add-version.png

@@ -479,6 +479,10 @@ When you receive this error, you have two options. Either move your resources to
 
 No, you can't move a resource group to a new subscription. But, you can move all of the resources in the resource group to a resource group in another subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group. You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
 
+### Unsupported scenarios
+
+The platform blocks a scenario where resources from Subscription A are migrated to Subscription B when *at the same time* resources from Subscription B are migrated to Subscription C. This is by design.
+
 ## Next steps
 
 For a list of which resources support move, see [Move operation support for resources](move-support-resources.md).

articles/api-center/media/register-apis/apis-page.png

@@ -17,8 +17,108 @@ Microsoft recommends [Application Insights](/azure/azure-monitor/app/app-insight
 
 Learn how modern monitoring with Azure Monitor can transform your business by reviewing the [product overview, features, getting started guide and more](https://azure.microsoft.com/services/monitor).
 
+### Azure Resource Health for Azure VMware Solution Private Cloud (Public preview)
+
+In this article, you learn how Azure Resource Health helps you diagnose and get support for service problems that affect your Private Cloud resources. Azure Resource Health reports on the current and past health of your Private Cloud Infrastructure resources and provides you with a personalized dashboard of the health of the infrastructure resources. Azure Resource Health allows you to report on historical events and can identify every time a service is unavailable and if Service Level Agreement (SLA) is violated. 
+
+#### Preview Enablement
+
+You are required to register yourself for the feature preview under _Preview Features_ of Azure VMware Solution in Azure portal. Customers should first register themselves to ***"Microsoft.AVS/ResourceHealth"*** preview flag from Azure portal and once registered, all the preconfigured alerts related to Host replacement, vCenter, and other critical alarms will start to surface in the Resource Health of Azure VMware Solution (AVS) User Interface (UI).
+
+#### Benefits of enabling Resource Health
+
+- Resource Health feature enablement adds significant value to your monitoring capabilities. You get notified about unplanned maintenance that took place in your private cloud infrastructure.
+
+- Resource Health gives you a personalized dashboard of the health of your resources. Resource Health shows all the time that your resources have been unavailable which makes it easy for you to check if SLA was violated.
+
+- For the Public Preview, a group of critical alerts are enabled which notifies you about Host replacements, storage critical alarms and also about the Network health of your private cloud.
+
+- The alerts are updated to have all the necessary information for better reporting and triage purposes.
+
+- Resource Health uses Azure Action groups that allow you to configure Email/SMS/Webhook/ITSM and get notified via communication method of your choice.
+
+- Once Enabled the health of your private cloud infrastructure reflects following statuses
+
+  
+  - Available
+  
+  - Unavailable
+
+  - Unknown
+
+  - Degraded
+
+
+#### Available 
+
+Available means that there are no events detected that affect the health of the resource. In cases where the resource recovered from unplanned downtime during the last 24 hours, you see a "Recently resolved" notification
+
+
+
+#### Unavailable 
+
+Unavailable means that the service detected an ongoing platform or nonplatform event that affects the health of the resource.
+
+#### Unknown
+
+Unknown means that Resource Health hasn't received information about the resource for more than 10 minutes. You may see this status under two different conditions: 
+
+- Your subscription is not enabled for Resource Health metrics, and you need to register yourself for the preview.
+
+- If the resource is running as expected, the status of the resource will change to Available after a few minutes. If you experience problems with the resource, the Unknown health status might mean that an event in the private cloud is affecting the resource.
+
+
+
+#### Degraded
+
+Degraded means that Resource Health detected a loss in performance in either one or more private cloud resources, although it's still available for use. Different resources have their own criteria for when they report that they are degraded.
+
+
+
+#### Pre-configured Alarms enabled in Azure Resource Health
+
+
+|Alert Name|Remediation Mode|
+| -------- | -------- |
+|Physical Disk Health Alarm |System Remediation|
+|System Board Health Alarm|System Remediation|
+| Memory Health Alarm|System Remediation|
+|Storage Health Alarm|System Remediation|
+|Temperature Health Alarm |System Remediation|
+|Host Connection State Alarm|System Remediation|
+|High Availability (HA) host Status |System Remediation|
+| Network Connectivity Lost Alarm|System Remediation|
+|Virtual Storage (vSAN) Host Disk Error Alarm|System Remediation|
+|Voltage Health Alarm |System Remediation|
+|Processor Health Alarm| System Remediation|
+|Fan Health Alarm|System Remediation|
+|High pNIC error rate detected|System Remediation|
+|iDRAC critical alerts if there are hardware faults (CPU/DIMM/PCI bus/Voltage issues)|System Remediation|
+|vSphere HA restarted a virtual machine|System Remediation|
+|Virtual Storage (vSAN) High Disk Utilization|Customer Intervention Required|
+|Replacement Start and Stop Notification|System Remediation|
+|Repair Service notification to customers (Host reboot and Restart of Management services) |System Remediation|
+|Notification to customer when a Virtual Machine is configured to use an external device that prevents a maintenance operation|Customer Intervention Required|
+| Customer notification when CD-ROM is mounted on the Virtual Machine and its ISO image isn't accessible and blocks maintenance operation|Customer Intervention Required|
+|Notification to customer when an external Datastore mounted becomes inaccessible and will block maintenance operations|Customer Intervention Required|
+|Notification to customer when connected network adapter becomes inaccessible and blocks any maintenance operations|Customer Intervention Required|
+|VMware Network (NSX –T) alarms (Customer notification about License expiration)|Customer Intervention Required|
+
+
+## Next Steps
+
+Now that you have configured an alert rule for your Azure VMware Solution private cloud, you can learn more about: 
+
+-  [Azure Resource Health](/azure/service-health/resource-health-overview)
+
+-  [Azure Monitor](/azure/azure-monitor/overview)
+
+-  [Azure Action Groups](/azure/azure-monitor/alerts/action-groups)
+
+You can also continue with one of the other Azure VMware Solution how-to [guides](/azure/azure-vmware/deploy-azure-vmware-solution?tabs=azure-portal)
+
 ## Third-party solutions
-Our application performance monitoring and troubleshooting partners have industry-leading solutions in VMware-based environments that assure the availability, reliability, and responsiveness of applications and services. Our customers adopt many of the solutions integrated with VMware NSX-T Data Center for their on-premises deployments. As one of our key principles, we want to enable them to continue to use their investments and VMware solutions running on Azure. Many of the Independent Software Vendors (ISV) already validated their solutions with Azure VMware Solution.
+Our application performance monitoring and troubleshooting partners have industry-leading solutions in VMware-based environments that assure the availability, reliability, and responsiveness of applications and services. You can adopt many of the solutions integrated with VMware NSX-T Data Center for their on-premises deployments. As one of our key principles, we want to enable you to continue to use your investments and VMware solutions running on Azure. Many of the Independent Software Vendors (ISV) already validated their solutions with Azure VMware Solution.
 
 You can find more information about these solutions here: