Merge pull request #285875 from MicrosoftDocs/main

8/30 11:00 AM IST Publish

Author: PhilKang0704

articles/azure-resource-manager/managed-applications/media/update-managed-resources/assignment.png

@@ -3,12 +3,12 @@ title: Update managed resources
 description: Describes how to work on resources in the managed resource group for an Azure managed application.
 ms.topic: how-to
 ms.custom: devx-track-azurecli
-ms.date: 06/24/2024
+ms.date: 08/29/2024
 ---
 
 # Work with resources in the managed resource group for Azure managed application
 
-This article describes how to update resources that are deployed as part of a managed application. As the publisher of a managed application, you have access to the resources in the managed resource group. To update these resources, you need to find the managed resource group associated with a managed application, and access the resource in that resource group.
+This article describes how to update resources that are deployed as part of a managed application. As the publisher of a managed application, you have management access to resources in the managed resource group in the customer's Azure tenant. To update these resources, you need to sign in to the customer's subscription, find the managed resource group associated with a managed application, and access the resources in the managed resource group. For more information about permissions, see [Publisher and customer permissions](./overview.md#publisher-and-customer-permissions).
 
 This article assumes you deployed the managed application in the [Managed Web Application (IaaS) with Azure management services](https://github.com/Azure/azure-managedapp-samples/tree/master/Managed%20Application%20Sample%20Packages/201-managed-web-app) sample project. That managed application includes a **Standard_D1_v2** virtual machine. If you didn't deploy that managed application, you can still use this article to become familiar with the steps for updating a managed resource group.
 
@@ -26,30 +26,30 @@ In this article, you use Azure CLI to:
 
 ## Get managed application and managed resource group
 
-To get the managed applications in a resource group, use:
+To get the managed applications in a resource group, use the following commands. Replace `<resourceGroupName>` with your resource group name.
 
 ```azurecli-interactive
-az managedapp list --query "[?contains(resourceGroup,'DemoApp')]"
+az managedapp list --query "[?contains(resourceGroup,'<resourceGroupName>')]"
 ```
 
 To get the ID of the managed resource group, use:
 
 ```azurecli-interactive
-az managedapp list --query "[?contains(resourceGroup,'DemoApp')].{ managedResourceGroup:managedResourceGroupId }"
+az managedapp list --query "[?contains(resourceGroup,'<resourceGroupName>')].{ managedResourceGroup:managedResourceGroupId }"
 ```
 
 ## Resize VMs in managed resource group
 
-To see the virtual machines in the managed resource group, provide the name of the managed resource group.
+To see the virtual machines in the managed resource group, provide the name of the managed resource group. Replace `<mrgName>` with your managed resource group's name.
 
 ```azurecli-interactive
-az vm list -g DemoApp6zkevchqk7sfq --query "[].{VMName:name,OSType:storageProfile.osDisk.osType,VMSize:hardwareProfile.vmSize}"
+az vm list -g <mrgName> --query "[].{VMName:name,OSType:storageProfile.osDisk.osType,VMSize:hardwareProfile.vmSize}"
 ```
 
 To update the size of the VMs, use:
 
 ```azurecli-interactive
-az vm resize --size Standard_D2_v2 --ids $(az vm list -g DemoApp6zkevchqk7sfq --query "[].id" -o tsv)
+az vm resize --size Standard_D2_v2 --ids $(az vm list -g <mrgName> --query "[].id" -o tsv)
 ```
 
 After the operation completes, verify the application is running on Standard D2 v2.
@@ -58,10 +58,10 @@ After the operation completes, verify the application is running on Standard D2
 
 ## Apply policy to managed resource group
 
-Get the managed resource group and assignment a policy at that scope. The policy **e56962a6-4747-49cd-b67b-bf8b01975c4c** is a built-in policy for specifying allowed locations.
+Get the managed resource group and assign a policy at that scope. The policy **e56962a6-4747-49cd-b67b-bf8b01975c4c** is a built-in policy to specify allowed locations.
 
 ```azurecli-interactive
-managedGroup=$(az managedapp show --name <app-name> --resource-group DemoApp --query managedResourceGroupId --output tsv)
+managedGroup=$(az managedapp show --name <app-name> --resource-group <resourceGroupName> --query managedResourceGroupId --output tsv)
 
 az policy assignment create --name locationAssignment --policy e56962a6-4747-49cd-b67b-bf8b01975c4c --scope $managedGroup --params '{
                             "listofallowedLocations": {
@@ -85,5 +85,5 @@ The policy assignment appears in the portal.
 
 ## Next steps
 
-- For an introduction to managed applications, see [Managed application overview](overview.md).
+- For an introduction to managed applications, see [Azure Managed Applications overview](overview.md).
 - For sample projects, see [Sample projects for Azure managed applications](sample-projects.md).

articles/azure-resource-manager/managed-applications/media/update-managed-resources/deployed.png

@@ -47,7 +47,7 @@ This guide walks you through purging assets from all edge nodes of an endpoint.
 	3. **Root domain purge**: Purge the root of the endpoint with "/" in the path.
 
    > [!TIP]
-   > 1. Paths must be specified for purge and must be a relative URL that fit the following [RFC 3986 - Uniform Resource Identifier (URI: Generic Syntax](https://datatracker.ietf.org/doc/html/rfc3986#section-3.3).
+   > 1. Paths must be specified for purge and must be a relative URL that fit the following [RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax](https://datatracker.ietf.org/doc/html/rfc3986#section-3.3).
    >
    > 1. In Azure CDN from Microsoft, query strings in the purge URL path are not considered. If the path to purge is provided as `/TestCDN?myname=max`, only `/TestCDN` is considered. The query string `myname=max` is omitted. Both `TestCDN?myname=max` and `TestCDN?myname=clark` will be purged.
 

articles/azure-resource-manager/managed-applications/media/update-managed-resources/upgraded.png

@@ -38,9 +38,7 @@ For example, if your usage has product **Red Hat Enterprise Linux - 1-4 vCPU VM
 
 Get the product name from your usage data and buy the SUSE plan with the same type and size.
 
-For example, if your usage is for product **SUSE Linux Enterprise Server Priority - 2-4 vCPU VM Support**, you should purchase **SUSE Linux Enterprise Server Priority** for **2-4 vCPU**.
-
-:::image type="content" border="true" source="./media/understand-suse-reservation-charges/select-suse-linux-enterprise-server-priority-2-4-vcpu.png" alt-text="Screenshot that shows selecting the product to purchase.":::
+For example, if your usage is for product **SUSE for SAP Linux Enterprise Server** **- 2-4 vCPU VM Support**, you should purchase **SUSE for SAP Linux Enterprise Server** for **2-4 vCPU**.
 
 ## Discount applies to different VM sizes for SUSE plans
 
@@ -68,13 +66,13 @@ The following tables show the software plans you can buy a reservation for, thei
 |SUSE Linux Enterprise Server for HPC 3-4 vCPUs|4ed70d2d-e2bb-4dcd-b6fa-42da71861a1c|1.92308|D4s_v3|
 |SUSE Linux Enterprise Server for HPC 5+ vCPUs |907a85de-024f-4dd6-969c-347d47a1bdff|2.92308|D8s_v3|
 
-### SUSE Linux Enterprise Server for SAP applications
+### SUSE for SAP Linux Enterprise Server
 
 |SUSE VM | MeterId | Ratio|Example VM size|
 | ------- |------------------------| --- | --- |
-|SUSE Linux Enterprise Server for SAP applications 1-2 vCPUs|497fe0b6-fa3c-4e3d-a66b-836097244142|1|D2s_v3|
-|SUSE Linux Enterprise Server for SAP applications 3-4 vCPUs |847887de-68ce-4adc-8a33-7a3f4133312f|2|D4s_v3|
-|SUSE Linux Enterprise Server for SAP applications 5+ vCPUs |18ae79cd-dfce-48c9-897b-ebd3053c6058|2.41176|D8s_v3|
+|SUSE for SAP Linux Enterprise Server 1-2 vCPUs|797618eb-cecb-59e7-a10e-1ee1e4e62d32|1|D2s_v3|
+|SUSE for SAP Linux Enterprise Server 3-4 vCPUs |1c0fb48a-e518-53c2-ab56-6feddadbb9a3|2|D4s_v3|
+|SUSE for SAP Linux Enterprise Server 5+ vCPUs |3ce5649c-142b-5a59-9b2a-6889da9b56f5|2.41176|D8s_v3|
 
 ### SUSE Linux Enterprise Server
 

articles/azure-resource-manager/managed-applications/update-managed-resources.md

@@ -45,16 +45,16 @@ The record set name given must be a *relative* name, meaning it must exclude the
 
 If a new record set is created, a default time-to-live (TTL) of 3600 is used. For instructions on how to use different TTLs, see [Create a DNS record set](#create-a-dns-record-set).
 
-The following example creates an A record called *www* in the zone *contoso.com* in the resource group *MyResourceGroup*. The IP address of the A record is *1.2.3.4*.
+The following example creates an A record called *www* in the zone *contoso.com* in the resource group *MyResourceGroup*. The IP address of the A record is *203.0.113.11*.
 
 ```azurecli-interactive
-az network dns record-set a add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name www --ipv4-address 1.2.3.4
+az network dns record-set a add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name www --ipv4-address 203.0.113.11
 ```
 
 To create a record set in the apex of the zone (in this case, "contoso.com"), use the record name "\@", including the quotation marks:
 
 ```azurecli-interactive
-az network dns record-set a add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name "@" --ipv4-address 1.2.3.4
+az network dns record-set a add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name "@" --ipv4-address 203.0.113.11
 ```
 
 ## Create a DNS record set
@@ -92,7 +92,7 @@ There's no example for create an SOA record set, since SOAs are created and dele
 ### Create an AAAA record
 
 ```azurecli-interactive
-az network dns record-set aaaa add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name test-aaaa --ipv6-address 2607:f8b0:4009:1803::1005
+az network dns record-set aaaa add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name test-aaaa --ipv6-address FD00::1
 ```
 
 ### Create a CAA record
@@ -123,7 +123,7 @@ az network dns record-set mx add-record --resource-group myresourcegroup --zone-
 ### Create an NS record
 
 ```azurecli-interactive
-az network dns record-set ns add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name test-ns --nsdname ns1.contoso.com
+az network dns record-set ns add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name test-ns --nsdname ns1.fabrikam.com
 ```
 
 ### Create a PTR record
@@ -192,10 +192,10 @@ This command deletes a DNS record from a record set. If the last record in a rec
 
 When you use the `az network dns record-set <record-type> add-record` command, you need to specify the record getting deleted and the zone to delete from. These parameters are described in [Create a DNS record](#create-a-dns-record) and [Create records of other types](#create-records-of-other-types) above.
 
-The following example deletes the A record with value '1.2.3.4' from the record set named *www* in the zone *contoso.com*, in the resource group *MyResourceGroup*.
+The following example deletes the A record with value '203.0.113.11' from the record set named *www* in the zone *contoso.com*, in the resource group *MyResourceGroup*.
 
 ```azurecli-interactive
-az network dns record-set a remove-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name "www" --ipv4-address 1.2.3.4
+az network dns record-set a remove-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name "www" --ipv4-address 203.0.113.11
 ```
 
 ## Modify an existing record set
@@ -206,11 +206,11 @@ Each record set contains a [time-to-live (TTL)](dns-zones-records.md#time-to-liv
 
 To modify an existing record of type A, AAAA, CAA, MX, NS, PTR, SRV, or TXT, you should first add a new record and then delete the existing record. For detailed instructions on how to delete and add records, see the earlier sections of this article.
 
-The following example shows how to modify an 'A' record, from IP address 1.2.3.4 to IP address 5.6.7.8:
+The following example shows how to modify an 'A' record, from IP address 203.0.113.11 to IP address 203.0.113.22:
 
 ```azurecli-interactive
-az network dns record-set a add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name www --ipv4-address 5.6.7.8
-az network dns record-set a remove-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name www --ipv4-address 1.2.3.4
+az network dns record-set a add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name www --ipv4-address 203.0.113.22
+az network dns record-set a remove-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name www --ipv4-address 203.0.113.11
 ```
 
 You can't add, remove, or modify the records in the automatically created NS record set at the zone apex (`--Name "@"`, including quote marks). For this record set, the only changes permitted are to modify the record set TTL and metadata.
@@ -250,7 +250,7 @@ This restriction applies only to the NS record set at the zone apex. Other NS re
 The following example shows how to add another name server to the NS record set at the zone apex:
 
 ```azurecli-interactive
-az network dns record-set ns add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name "@" --nsdname ns1.myotherdnsprovider.com 
+az network dns record-set ns add-record --resource-group myresourcegroup --zone-name contoso.com --record-set-name "@" --nsdname ns1.fabrikam.com 
 ```
 
 ### To modify the TTL of an existing record set

articles/cdn/cdn-purge-endpoint.md

@@ -19,6 +19,9 @@ You can connect to an Azure Data Manager for Energy instance that's configured w
 
 This article describes how to set up a private endpoint for Azure Data Manager for Energy. 
 
+> [!NOTE]
+> To enable private endpoint, public access must be disabled for Azure Data Manager for Energy. If public access is enabled and private endpoint is created, the instance will only be accessed via private endpoint and not by public access.
+
 > [!NOTE]
 > Terraform currently does not support private endpoint creation for Azure Data Manager for Energy.