Merge pull request #288776 from meganbradley/meganbradley/docutune-autopr-20241020-030949-3847684-ignore-build

[BULK] - DocuTune remediation - Sensitive terms with GUIDs (part 16)

Author: prmerger-automator[bot]

articles/azure-netapp-files/azacsnap-configure-storage.md

@@ -116,10 +116,10 @@ az role assignment create --assignee ${PRINCIPAL_ID} --role "AzAcSnap on ANF" --
 
     ```output
     {
-      "clientId": "00aa000a-aaaa-0000-00a0-00aa000aaa0a",
-      "clientSecret": "00aa000a-aaaa-0000-00a0-00aa000aaa0a",
-      "subscriptionId": "00aa000a-aaaa-0000-00a0-00aa000aaa0a",
-      "tenantId": "00aa000a-aaaa-0000-00a0-00aa000aaa0a",
+      "clientId": "00001111-aaaa-2222-bbbb-3333cccc4444",
+      "clientSecret": "Dd4Ee~5Ff6.-Gg7Hh8Ii9Jj0Kk1Ll2_Mm3Nn4Oo5",
+      "subscriptionId": "cccc2c2c-dd3d-ee4e-ff5f-aaaaaa6a6a6a",
+      "tenantId": "aaaabbbb-0000-cccc-1111-dddd2222eeee",
       "activeDirectoryEndpointUrl": "https://login.microsoftonline.com",
       "resourceManagerEndpointUrl": "https://management.azure.com/",
       "activeDirectoryGraphResourceId": "https://graph.windows.net/",

articles/azure-netapp-files/configure-application-volume-group-sap-hana-api.md

@@ -127,13 +127,13 @@ The following properties are available with [Application volume group for SAP HA
 The examples in this section illustrate the values passed in the volume group creation request for various SAP HANA configurations. The examples demonstrate best practices for naming, sizing, and values as described in the tables.
 
 In the following examples, selected placeholders are specified. You should replace them with the values specific to your configuration. These values include:
-1.	`<SubscriptionId>`: Subscription ID. Example: `11111111-2222-3333-4444-555555555555`
+1.	`<SubscriptionId>`: Subscription ID. Example: `aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e`
 2.	`<ResourceGroup>`: Resource group. Example: `TestResourceGroup`
 3.	`<NtapAccount>`: NetApp account, for example: `TestAccount`
 4.	`<VolumeGroupName>`: Volume group name, for example: `SH9-Test-00001`
-5.	`<SubnetId>`: Subnet resource ID, for example: `/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/myRP/providers/Microsoft.Network/virtualNetworks/testvnet3/subnets/SH9_Subnet`
-6. `<CapacityPoolResourceId>`: Capacity pool resource ID, for example: `/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/SH9_Pool`
-7.	`<ProximityPlacementGroupResourceId>`: Proximity placement group, for example: `/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/test/providers/Microsoft.Compute/proximityPlacementGroups/SH9_PPG`
+5.	`<SubnetId>`: Subnet resource ID, for example: `/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/myRP/providers/Microsoft.Network/virtualNetworks/testvnet3/subnets/SH9_Subnet`
+6. `<CapacityPoolResourceId>`: Capacity pool resource ID, for example: `/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/SH9_Pool`
+7.	`<ProximityPlacementGroupResourceId>`: Proximity placement group, for example: `/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/test/providers/Microsoft.Compute/proximityPlacementGroups/SH9_PPG`
 8.	`<PartnerVolumeId>`: Partner volume ID (for HSR volumes).
 9.	`<ExampleJson>`: JSON Request from one of the examples in the API request tables below.
 
@@ -1143,8 +1143,8 @@ Cross-region replication is one way to set up a disaster recovery configuration
 
 In this example, the following placeholders are specified and should be replaced by values specific to your configuration:
 1.	`<CapacityPoolResourceId3>`: DR capacity pool resource ID, for example:
-`/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/DR_SH9_HSR_Pool`
-2.	`<ProximityPlacementGroupResourceId3>`: DR proximity placement group, for example:`/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/test/providers/Microsoft.Compute/proximityPlacementGroups/DR_SH9_PPG`
+`/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/DR_SH9_HSR_Pool`
+2.	`<ProximityPlacementGroupResourceId3>`: DR proximity placement group, for example:`/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/test/providers/Microsoft.Compute/proximityPlacementGroups/DR_SH9_PPG`
 3.	`<SrcVolumeId_data>`, `<SrcVolumeId_shared>`, `<SrcVolumeId_data-backup>`, `<SrcVolumeId_log-backup>`: cross-region replication source volume IDs for the data, shared, and log-backup cross-region replication destination volumes.
 
 ```json

articles/azure-netapp-files/configure-application-volume-oracle-api.md

@@ -76,17 +76,17 @@ The examples in this section illustrate the values passed in the volume group cr
 In the following examples, selected placeholders are specified. You should replace them with values specific to your configuration. These values include:
 
 * `<SubscriptionId>`:  
-    Subscription ID. Example: `11111111-2222-3333-4444-555555555555`
+    Subscription ID. Example: `aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e`
 * `<ResourceGroup>`:  
     Resource group. Example: `TestResourceGroup`
 * `<NtapAccount>`:  
     NetApp account. Example: `TestAccount`
 * `<VolumeGroupName>`:  
     Volume group name. Example: `SH9-Test-00001`
 * `<SubnetId>`:  
-    Subnet resource ID. Example: `/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/myRP/providers/Microsoft.Network/virtualNetworks/testvnet3/subnets/SH9_Subnet`
+    Subnet resource ID. Example: `/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/myRP/providers/Microsoft.Network/virtualNetworks/testvnet3/subnets/SH9_Subnet`
 * `<CapacityPoolResourceId>`:  
-    Capacity pool resource ID. Example: `/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/SH9_Pool `
+    Capacity pool resource ID. Example: `/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/myRG/providers/Microsoft.NetApp/netAppAccounts/account1/capacityPools/SH9_Pool `
 
 ## Create application volume groups for Oracle using curl
 
@@ -1127,4 +1127,4 @@ curl -X PUT -H "Authorization: Bearer $token" -H "Content-Type:application/json"
 * [Deploy application volume group for Oracle using Azure Resource Manager](configure-application-volume-oracle-azure-resource-manager.md) 
 * [Troubleshoot application volume group errors](troubleshoot-application-volume-groups.md)
 * [Delete an application volume group](application-volume-group-delete.md)
-* [Application volume group FAQs](faq-application-volume-group.md)
+* [Application volume group FAQs](faq-application-volume-group.md)

articles/azure-netapp-files/troubleshoot-volumes.md

@@ -55,7 +55,7 @@ If a volume create-read-update-delete (CRUD) operation is performed on a volume
 |-|---|
 | Error when creating an SMB volume with LDAP enabled as true: <br> `Error Message: ldapEnabled option is only supported with NFS protocol volume. ` | You cannot create an SMB volume with LDAP enabled. <br> Create SMB volumes with LDAP disabled. |
 | Error when updating the ldapEnabled parameter value for an existing volume: <br> `Error Message: ldapEnabled parameter is not allowed to update` |  You cannot modify the LDAP option setting after creating a volume. <br> Do not update the LDAP option setting on a created volume. See [Configure AD DS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md) for details. |
-| Error when creating an LDAP-enabled NFS volume: <br> `Could not query DNS server` <br> `Sample error message:` <br> `"log": time="2020-10-21 05:04:04.300" level=info msg=Res method=GET url=/v2/Volumes/070d0d72-d82c-c893-8ce3-17894e56cea3  x-correlation-id=9bb9e9fe-abb6-4eb5-a1e4-9e5fbb838813 x-request-id=c8032cb4-2453-05a9-6d61-31ca4a922d85 xresp="200:  {\"created\":\"2020-10-21T05:02:55.000Z\",\"lifeCycleState\":\"error\",\"lifeCycleStateDetails\":\"Error when creating - Could not query DNS server. Verify that the network configuration is correct and that DNS servers are available.\",\"name\":\"smb1\",\"ownerId\ \":\"8c925a51-b913-11e9-b0de-9af5941b8ed0\",\"region\":\"westus2stage\",\"volumeId\":\"070d0d72-d82c-c893-8ce3-` |  This error occurs because DNS is unreachable. <br> <ul><li> Check if you've configured the correct site (site scoping) for Azure NetApp Files. </li><li> The reason that DNS is unreachable might be an incorrect DNS IP address or networking issues. Check the DNS IP address entered in the AD connection to make sure that it is correct. </li><li> If you're using Basic network features, ensure that the AD and the volume are in the same region and the same VNet. If they are in different VNets, ensure that VNet peering is established between the two VNets.</li></ul> |
+| Error when creating an LDAP-enabled NFS volume: <br> `Could not query DNS server` <br> `Sample error message:` <br> `"log": time="2020-10-21 05:04:04.300" level=info msg=Res method=GET url=/v2/Volumes/070d0d72-d82c-c893-8ce3-17894e56cea3  x-correlation-id=aaaa0000-bb11-2222-33cc-444444dddddd x-request-id=bbbb1111-cc22-3333-44dd-555555eeeeee xresp="200:  {\"created\":\"2020-10-21T05:02:55.000Z\",\"lifeCycleState\":\"error\",\"lifeCycleStateDetails\":\"Error when creating - Could not query DNS server. Verify that the network configuration is correct and that DNS servers are available.\",\"name\":\"smb1\",\"ownerId\ \":\"cccc2222-dd33-4444-55ee-666666ffffff\",\"region\":\"westus2stage\",\"volumeId\":\"070d0d72-d82c-c893-8ce3-` |  This error occurs because DNS is unreachable. <br> <ul><li> Check if you've configured the correct site (site scoping) for Azure NetApp Files. </li><li> The reason that DNS is unreachable might be an incorrect DNS IP address or networking issues. Check the DNS IP address entered in the AD connection to make sure that it is correct. </li><li> If you're using Basic network features, ensure that the AD and the volume are in the same region and the same VNet. If they are in different VNets, ensure that VNet peering is established between the two VNets.</li></ul> |
 | Error when creating volume from a snapshot: <br> `Aggregate does not exist` | Azure NetApp Files doesn’t support provisioning a new, LDAP-enabled volume from a snapshot that belongs to an LDAP-disabled volume. <br> Try creating new an LDAP-disabled volume from the given snapshot. |
 | When only primary group IDs are seen and user belongs to auxiliary groups too. | This is caused by a query timeout: <br> -Use [LDAP search scope option](configure-ldap-extended-groups.md). <br> -Use [preferred Active Directory servers for LDAP client](create-active-directory-connections.md#preferred-server-ldap). |
 | `Error describing volume - Entry doesn't exist for username: <username>, please try with a valid username` | -Check if the user is present on LDAP server. <br> -Check if the LDAP server is healthy. |