Merge branch 'MicrosoftDocs:main' into main

EthanChangAED · web-flow · commit 0e7010b3b563 · 2024-11-29T17:45:53.000+08:00
diff --git a/articles/energy-data-services/how-to-deploy-gcz.md b/articles/energy-data-services/how-to-deploy-gcz.md
@@ -21,6 +21,7 @@ This guide shows you how to deploy the Geospatial Consumption Zone (GCZ) service
 To deploy the GCZ, you need to create an App Registration in Microsoft Entra ID. The App Registration is used to authenticate the GCZ APIs with Azure Data Manager for Energy to be able to generate the cache of the geospatial data.
 
 1. See [Create an App Registration in Microsoft Entra ID](/azure/active-directory/develop/quickstart-register-app) for instructions on how to create an App Registration.
+
 1. Grant the App Registration permission to read the relevant data in Azure Data Manager for Energy. See [How to add members to an OSDU group](./how-to-manage-users.md#add-members-to-an-osdu-group-in-a-data-partition) for further instructions.
 
 ## Setup
@@ -63,6 +64,7 @@ Through APIM we can add policies to secure, monitor, and manage the APIs.
 1. Download the two OpenAPI specification to your local computer.
    - [GCZ Provider](https://github.com/microsoft/adme-samples/blob/main/services/gcz/gcz-openapi-provider.yaml)
    - [GCZ Transformer](https://github.com/microsoft/adme-samples/blob/main/services/gcz/gcz-openapi-transformer.yaml)
+
 1. Open each OpenAPI specification file in a text editor and replace the `servers` section with the corresponding IPs of the AKS GCZ Services' Load Balancer.
 
    ```yaml
@@ -82,8 +84,8 @@ Through APIM we can add policies to secure, monitor, and manage the APIs.
 
 ## Testing the GCZ service
 
-1. Download the API client collection from the [OSDU GitLab](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/blob/master/docs/test-assets/postman/Geospatial%20Consumption%20Zone%20-%20Provider%20Postman%20Tests.postman_collection.json?ref_type=heads) and import it into your API client of choice (that is, Bruno, Postman).
-1.
+1. Download the API client collection from the [OSDU GitLab](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/blob/master/docs/test-assets/postman/Geospatial%20Consumption%20Zone%20-%20Provider%20Postman%20Tests.postman_collection.json?ref_type=heads) and import it into your API client of choice (i.e. Bruno, Postman).
+
 1. Add the following environment variables to your API client:
 
    - `PROVIDER_URL` - The URL to the GCZ Provider API.
diff --git a/articles/energy-data-services/includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md b/articles/energy-data-services/includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
@@ -115,7 +115,6 @@ Learn how to deploy Geospatial Consumption Zone (GCZ) on Azure Kubernetes Servic
                type: LoadBalancer
            configuration:
                privateNetwork: "$PRIVATE_NETWORK"
-           configLoaderJs: "../../../../gcz-provider/gcz-provider-core/config/configLoader.js"
        transformer:
            namespace: $NAMESPACE
            image:
@@ -174,7 +173,6 @@ Learn how to deploy Geospatial Consumption Zone (GCZ) on Azure Kubernetes Servic
                type: LoadBalancer
            configuration:
                privateNetwork: "$PRIVATE_NETWORK"
-           configLoaderJs: "../../../../gcz-provider/gcz-provider-core/config/configLoader.js"
        transformer:
            namespace: $NAMESPACE
            image:
@@ -318,7 +316,7 @@ Learn how to deploy Geospatial Consumption Zone (GCZ) on Azure Kubernetes Servic
 1. Deploy the GCZ HELM chart:
 
    ```bash
-   helm upgrade -i $CHART . -n $NAMESPACE -f osdu_gcz_custom_values.yaml
+   helm upgrade -i $CHART . -n $NAMESPACE -f osdu_gcz_custom_values.yaml --set-file global.provider.configLoaderJs="gcz-provider/gcz-provider-core/config/configLoader.js"
    ```
 
 1. Verify the deployment:
diff --git a/articles/migrate/vmware/agent-based-migration-architecture.md b/articles/migrate/vmware/agent-based-migration-architecture.md
@@ -6,7 +6,7 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 12/12/2022
+ms.date: 09/26/2024
 ms.custom: vmware-scenario-422, engagement-fy23
 ---
 
diff --git a/articles/migrate/vmware/concepts-vmware-agentless-migration.md b/articles/migrate/vmware/concepts-vmware-agentless-migration.md
@@ -6,7 +6,7 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 10/18/2023
+ms.date: 11/26/2024
 ms.custom: vmware-scenario-422, engagement-fy24
 ---
 # Agentless migration architecture
diff --git a/articles/migrate/vmware/how-to-automate-migration.md b/articles/migrate/vmware/how-to-automate-migration.md
@@ -6,7 +6,7 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 05/11/2023
+ms.date: 08/20/2024
 ms.custom: vmware-scenario-422, engagement-fy23
 ---
 
diff --git a/articles/migrate/vmware/how-to-migrate-vmware-vms-with-cmk-disks.md b/articles/migrate/vmware/how-to-migrate-vmware-vms-with-cmk-disks.md
@@ -4,8 +4,8 @@ description: Learn how to migrate VMware VMs to Azure with server-side encryptio
 author: v-sreedevank
 ms.author: v-sreedevank
 ms.topic: how-to
-ms.date: 05/31/2023
-ms.custom: vmware-scenario-422, devx-track-azurepowershell, engagement-fy23
+ms.date: 10/20/2024
+ms.custom: vmware-scenario-422, devx-track-azurepowershell, engagement-fy25
 
 ---
 
diff --git a/articles/migrate/vmware/how-to-set-up-appliance-vmware.md b/articles/migrate/vmware/how-to-set-up-appliance-vmware.md
@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 06/20/2024
+ms.date: 09/26/2024
 ms.custom: vmware-scenario-422, engagement-fy23
 ---
 
diff --git a/articles/migrate/vmware/migrate-support-matrix-vmware-migration.md b/articles/migrate/vmware/migrate-support-matrix-vmware-migration.md
@@ -6,8 +6,8 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 06/11/2024
-ms.custom: vmware-scenario-422, engagement-fy23
+ms.date: 10/16/2024
+ms.custom: vmware-scenario-422, engagement-fy25
 ---
 
 # Support matrix for VMware vSphere migration
diff --git a/articles/migrate/vmware/migrate-support-matrix-vmware.md b/articles/migrate/vmware/migrate-support-matrix-vmware.md
@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 11/04/2024
+ms.date: 11/06/2024
 ms.custom: vmware-scenario-422, engagement-fy24
 ---
 
diff --git a/articles/migrate/vmware/prepare-for-agentless-migration.md b/articles/migrate/vmware/prepare-for-agentless-migration.md
@@ -5,7 +5,7 @@ author: vijain
 ms.author: vijain
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 06/19/2024
+ms.date: 10/25/2024
 ms.custom: vmware-scenario-422, engagement-fy23, linux-related-content
 ---
 
diff --git a/articles/migrate/vmware/start-here-vmware.md b/articles/migrate/vmware/start-here-vmware.md
@@ -10,7 +10,7 @@ products:
   - vmware
   - azure-virtual-machines
   - azure-vmware-solution
-ms.date: 05/08/2024
+ms.date: 08/14/2024
 ms.custom: vmware-scenario-422
 
 # Customer intent - Overview  of the options for assessing an existing VMware deployment for migration
diff --git a/articles/migrate/vmware/troubleshoot-changed-block-tracking-replication.md b/articles/migrate/vmware/troubleshoot-changed-block-tracking-replication.md
@@ -6,7 +6,7 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: troubleshooting
 ms.service: azure-migrate
-ms.date: 10/18/2023
+ms.date: 08/08/2024
 ms.custom: vmware-scenario-422, engagement-fy24
 ---
 
diff --git a/articles/migrate/vmware/tutorial-assess-vmware-azure-vmware-solution.md b/articles/migrate/vmware/tutorial-assess-vmware-azure-vmware-solution.md
@@ -4,9 +4,9 @@ description: Learn how to assess servers in VMware environment for migration to
 author: jobingeorge-microsoft
 ms.author: jobingeorge
 ms.topic: tutorial
-ms.date: 07/19/2024
+ms.date: 11/06/2024
 ms.service: azure-migrate
-ms.custom: vmware-scenario-422, MVC, engagement-fy23
+ms.custom: vmware-scenario-422, MVC, engagement-fy25
 #Customer intent: As a VMware VM admin, I want to assess my VMware VMs in preparation for migration to Azure VMware Solution (AVS)
 ---
 
diff --git a/articles/migrate/vmware/tutorial-migrate-vmware-agent.md b/articles/migrate/vmware/tutorial-migrate-vmware-agent.md
@@ -6,7 +6,7 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 08/20/2024
+ms.date: 09/26/2024
 ms.custom: vmware-scenario-422, MVC, engagement-fy25
 ---
 
diff --git a/articles/migrate/vmware/tutorial-migrate-vmware-powershell.md b/articles/migrate/vmware/tutorial-migrate-vmware-powershell.md
@@ -5,7 +5,7 @@ author: vijain
 ms.author: vijain
 ms.manager: kmadnani
 ms.topic: tutorial
-ms.date: 01/24/2024
+ms.date: 10/20/2024
 ms.service: azure-migrate
 ms.custom: vmware-scenario-422, devx-track-azurepowershell, engagement-fy23
 ---
diff --git a/articles/migrate/vmware/tutorial-migrate-vmware.md b/articles/migrate/vmware/tutorial-migrate-vmware.md
@@ -6,8 +6,8 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 04/11/2024
-ms.custom: vmware-scenario-422, mvc, engagement-fy23
+ms.date: 11/16/2024
+ms.custom: vmware-scenario-422, mvc, engagement-fy24
 ---
 
 # Migrate VMware VMs to Azure (agentless)
diff --git a/articles/sap/center-sap-solutions/quickstart-register-system-cli.md b/articles/sap/center-sap-solutions/quickstart-register-system-cli.md
@@ -15,14 +15,14 @@ author: kalyaninamuduri
 The Azure CLI is used to create and manage Azure resources from the command line or in scripts. 
 
 [Azure Center for SAP solutions](overview.md) enables you to deploy and manage SAP systems on Azure. This article shows you how to register an existing SAP system running on Azure with *Azure Center for SAP solutions* using Az CLI. Alternatively, you can register systems using the Azure PowerShell or in the Azure portal.
-After you register an SAP system with *Azure Center for SAP solutions*, you can use its visualization, management and monitoring capabilities through the Azure portal. For example, you can:
+After you register an SAP system with *Azure Center for SAP solutions*, you can use its visualization, management, and monitoring capabilities through the Azure portal. For example, you can:
 
 This quickstart enables you to register an existing SAP system with *Azure Center for SAP solutions*.
 
 ## Prerequisites for registering a system
 - Check that you're trying to register a [supported SAP system configuration](/azure/sap/center-sap-solutions/register-existing-system#supported-systems)
 - Grant access to Azure Storage accounts from the virtual network where the SAP system exists. Use one of these options:
-    - Allow outbound internet connectivity for the VMs.
+    - Allow outbound internet connectivity for the Virtual Machines.
     - Use a [**Storage** service tag](../../virtual-network/service-tags-overview.md) to allow connectivity to any Azure storage account from the VMs.
     - Use a [**Storage** service tag with regional scope](../../virtual-network/service-tags-overview.md) to allow storage account connectivity to the Azure storage accounts in the same region as the VMs.
     - Allowlist the region-specific IP addresses for Azure Storage.
@@ -35,13 +35,13 @@ This quickstart enables you to register an existing SAP system with *Azure Cente
 - A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Compute resource group and **Reader** role access on the Virtual Network resource group of the SAP system. Azure Center for SAP solutions service uses this identity to discover your SAP system resources and register the system as a VIS resource.
 - Make sure ASCS, Application Server and Database virtual machines of the SAP system are in **Running** state.
 - sapcontrol and saphostctrl exe files must exist on ASCS, App server and Database.
-    - File path on Linux VMs: /usr/sap/hostctrl/exe
-    - File path on Windows VMs: C:\Program Files\SAP\hostctrl\exe\
+    - File path on Linux Virtual Machines: /usr/sap/hostctrl/exe
+    - File path on Windows Virtual Machines: C:\Program Files\SAP\hostctrl\exe\
 - Make sure the **sapstartsrv** process is running on all **SAP instances** and for **SAP hostctrl agent** on all the VMs in the SAP system.
-    - To start hostctrl sapstartsrv use this command for Linux VMs: 'hostexecstart -start'
-    - To start instance sapstartsrv use the command: 'sapcontrol -nr 'instanceNr' -function StartService S0S'
-    - To check status of hostctrl sapstartsrv use this command for Windows VMs: C:\Program Files\SAP\hostctrl\exe\saphostexec –status
-- For successful discovery and registration of the SAP system, ensure there is network connectivity between ASCS, App and DB VMs. 'ping' command for App instance hostname must be successful from ASCS VM. 'ping' for Database hostname must be successful from App server VM.
+    - To start hostctrl sapstartsrv, use this command for Linux Virtual Machines: 'hostexecstart -start'
+    - To start instance sapstartsrv, use the command: 'sapcontrol -nr 'instanceNr' -function StartService S0S'
+    - To check status of hostctrl sapstartsrv use this command for Windows Virtual Machines: C:\Program Files\SAP\hostctrl\exe\saphostexec –status
+- For successful discovery and registration of the SAP system, ensure there's network connectivity between ASCS, App, and DB VMs. 'ping' command for App instance hostname must be successful from ASCS Virtual Machine. 'ping' for Database hostname must be successful from App server Virtual Machine.
 - On App server profile, SAPDBHOST, DBTYPE, DBID parameters must have the right values configured for the discovery and registration of Database instance details.
 
 ## Register SAP system
@@ -58,12 +58,14 @@ To register an existing SAP system in Azure Center for SAP solutions:
           --central-server-vm <Virtual Machine resource ID> \ 
           --identity "{type:UserAssigned,userAssignedIdentities:{<Managed Identity resource ID>:{}}}" \
           --managed-rg-name "acss-C36" \
+          --managed-resources-network-access-type <private/public> \
      ```
     - **g** is used to specify the name of the existing Resource Group into which you want the Virtual Instance for SAP solutions resource to be deployed. It could be the same RG in which you have Compute, Storage resources of your SAP system or a different one. 
-    - **n** parameter is used to specify the SAP System ID (SID) that you are registering with Azure Center for SAP solutions.
-    - **environment** parameter is used to specify the type of SAP environment you are registering. Valid values are *NonProd* and *Prod*.
-    - **sap-product** parameter is used to specify the type of SAP product you are registering. Valid values are *S4HANA*, *ECC*, *Other*.
-    - **managed-rg-name** parameter is used to specify the name of the managed resource group which is deployed by ACSS service in your Subscription. This RG is unique for each SAP system (SID) you register. If you do not specify the name, ACSS service sets a name with this naming convention 'mrg-{SID}-{random string}'.
+    - **n** parameter is used to specify the SAP System ID (SID) that you're registering with Azure Center for SAP solutions.
+    - **environment** parameter is used to specify the type of SAP environment you're registering. Valid values are *NonProd* and *Prod*.
+    - **sap-product** parameter is used to specify the type of SAP product you're registering. Valid values are *S4HANA*, *ECC*, *Other*.
+    - **managed-rg-name** parameter is used to specify the name of the managed resource group which is deployed by ACSS service in your Subscription. This RG is unique for each SAP system (SID) you register. If you don't specify the name, ACSS service sets a name with this naming convention 'mrg-{SID}-{random string}'.
+    - **managed-resources-network-access-type** specifies the network access configuration for the resources that will be deployed in the Managed Resource Group. The options to choose from are Public and Private. If 'Private' is chosen, the Storage Account service tag should be enabled on the subnets in which the SAP VMs exist. This is required for establishing connectivity between VM extensions and the managed resource group storage account. This setting is currently applicable only to Storage Account.
 
 2. Once you trigger the registration process, you can view its status by getting the status of the Virtual Instance for SAP solutions resource that gets deployed as part of the registration process.
 
diff --git a/articles/sentinel/data-connectors/hyas-protect.md b/articles/sentinel/data-connectors/hyas-protect.md
@@ -13,7 +13,7 @@ ms.collection: sentinel-data-connector
 
 HYAS Protect provide logs based on reputation values - Blocked, Malicious, Permitted, Suspicious.
 
-This is autogenerated content. For changes, contact the solution provider.
+It's autogenerated content. For changes, contact the solution provider.
 
 ## Connector attributes
 
@@ -36,7 +36,7 @@ HYASProtectDnsSecurityLogs_CL
 
 ## Prerequisites
 
-To integrate with HYAS Protect (using Azure Functions) make sure you have: 
+To integrate with HYAS Protect (using Azure Functions) make sure, you have: 
 
 - **Microsoft.Web/sites permissions**: Read and write permissions to Azure Functions to create a Function App is required. [See the documentation to learn more about Azure Functions](/azure/azure-functions/).
 - **REST API Credentials/permissions**: **HYAS API Key** is required for making API calls.
@@ -56,7 +56,7 @@ To integrate with HYAS Protect (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the HYAS Protect data connector using an ARM Tempate.
+Use this method for automated deployment of the HYAS Protect data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -89,14 +89,14 @@ If you're already signed in, go to the next step.
 
 	c. Select **Create new Function App in Azure** (Don't choose the Advanced option)
 
-	d. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. HyasProtectLogsXXX).
+	d. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (for example, HyasProtectLogsXXX).
 
 	e. **Select a runtime:** Choose Python 3.8.
 
-	f. Select a location for new resources. For better performance and lower costs choose the same [region](https://azure.microsoft.com/regions/) where Microsoft sentinel is located.
+	f. Select a location for new resources. For better performance and lower costs, choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
 
-6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
-7. Go to Azure Portal for the Function App configuration.
+6. Deployment begins. A notification is displayed after your function app is created and the deployment package is applied.
+7. Go to Azure portal for the Function App configuration.
 
 
 **2. Configure the Function App**
@@ -111,7 +111,3 @@ If you're already signed in, go to the next step.
 . Once all application settings have been entered, click **Save**.
 
 
-
-## Next steps
-
-For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/hyas.microsoft-sentinel-solution-hyas-protect?tab=Overview) in the Azure Marketplace.
diff --git a/articles/sentinel/unified-connector-cef-device.md b/articles/sentinel/unified-connector-cef-device.md
@@ -129,7 +129,7 @@ Set your security solution to send syslog messages in CEF format to the proxy ma
 
 Set your security solution to send syslog messages in CEF format to the proxy machine. Make sure to send the logs to port 514 TCP on the machine IP address.
 
-1. Follow the directions to install the [ExtraHop Detection SIEM Connector bundle](https://learn.extrahop.com/extrahop-detection-siem-connector-bundle) on your Reveal(x) system. The **SIEM Connector** is required for this integration.
+1. Follow the directions to install the [ExtraHop Detection SIEM Connector bundle](https://learn.extrahop.com/) on your Reveal(x) system. The **SIEM Connector** is required for this integration.
 1. Enable the trigger for **ExtraHop Detection SIEM Connector - CEF**.
 1. Update the trigger with the ODS syslog targets you created. 
 
diff --git a/articles/sentinel/unified-connector-syslog-device.md b/articles/sentinel/unified-connector-syslog-device.md
@@ -321,7 +321,6 @@ This data connector was developed using RSA SecurID Authentication Manager versi
 
 1. Follow these instructions to configure the VMware ESXi to forward syslog:
 
-   - [VMware ESXi 3.5 and 4.x](https://kb.vmware.com/s/article/1016621)
    - [VMware ESXi 5.0+](https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.monitoring.doc/GUID-9F67DB52-F469-451F-B6C8-DAE8D95976E7.html)
 
 1. Use the IP address or hostname for the Linux device with the Linux agent installed as the **Destination IP** address.
