Merge pull request #293460 from MicrosoftDocs/main

ttorble · web-flow · commit e1914a8bb2a8 · 2025-01-23T12:07:58.000Z
Publish to live, Thursday 4 AM PST, 1/23
diff --git a/articles/energy-data-services/how-to-deploy-osdu-admin-ui.md b/articles/energy-data-services/how-to-deploy-osdu-admin-ui.md
@@ -144,6 +144,7 @@ There are two deployment options for the OSDU Admin UI:
     ```
 
 ## Deploy storage account
+
 1. Create resource group. Skip this step if the resource group exists already.
     
     ```azurecli
@@ -183,7 +184,7 @@ There are two deployment options for the OSDU Admin UI:
         --public-access blob
     ```
 
-### Build and deploy the web app
+### Configure the website
 
 1. Navigate to the `OSDUApp` folder.
     
@@ -282,11 +283,14 @@ Replace the values according to the explanation.
     }
     ...
 }
+
 ```
 
-   > [!NOTE]
-   > [OSDU Connector API](https://community.opengroup.org/osdu/ui/admin-ui-group/admin-ui-totalenergies/connector-api-totalenergies) is built as an interface between consumers and OSDU APIs wrapping some API chain calls and objects. Currently, it manages all operations and actions on project and scenario objects.
-      
+---
+
+> [!NOTE]
+> [OSDU Connector API](https://community.opengroup.org/osdu/ui/admin-ui-group/admin-ui-totalenergies/connector-api-totalenergies) is built as an interface between consumers and OSDU APIs wrapping some API chain calls and objects. Currently, it manages all operations and actions on project and scenario objects.
+
 1. Build the web UI.
     ```bash
     ng build
@@ -300,7 +304,7 @@ Replace the values according to the explanation.
         --destination '$web' \
         --overwrite
     ```
-    
+
 1. Fetch the website URL.
     ```bash
    echo $REDIRECT_URI
diff --git a/articles/migrate/vmware/tutorial-discover-vmware.md b/articles/migrate/vmware/tutorial-discover-vmware.md
@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 11/20/2024
+ms.date: 01/23/2025
 ms.service: azure-migrate
 ms.custom: vmware-scenario-422, mvc, subject-rbac-steps, engagement-fy24
 #Customer intent: As an VMware admin, I want to discover my on-premises servers running in a VMware environment.
@@ -41,7 +41,7 @@ Requirement | Details
 --- | ---
 **vCenter Server/ESXi host** | You need a server running vCenter Server version 8.0, 7.0, 6.7, 6.5, 6.0, or 5.5.<br /><br /> Servers must be hosted on an ESXi host running version 5.5 or later.<br /><br /> On the vCenter Server, allow inbound connections on TCP port 443 so that the appliance can collect configuration and performance metadata.<br /><br /> The appliance connects to vCenter Server on port 443 by default. If the server running vCenter Server listens on a different port, you can modify the port when you provide the vCenter Server details in the appliance configuration manager.<br /><br /> On the ESXi hosts, make sure that inbound access is allowed on TCP port 443 for discovery of installed applications and for agentless dependency analysis on servers.
 **Azure Migrate appliance** | vCenter Server must have these resources to allocate to a server that hosts the Azure Migrate appliance:<br /><br /> - 32 GB of RAM, 8 vCPUs, and approximately 80 GB of disk storage.<br /><br /> - An external virtual switch and internet access on the appliance server, directly or via a proxy.
-**Servers** | All Windows and Linux OS versions are supported for discovery of configuration and performance metadata. <br /><br /> For application discovery on servers, all Windows and Linux OS versions are supported. Check the [OS versions supported for agentless dependency analysis](migrate-support-matrix-vmware.md?pivots=dependency-analysis-agentless-requirements&tabs=businesscase).<br /><br /> For discovery of installed applications and for agentless dependency analysis, VMware Tools (version 10.2.1 or later) must be installed and running on servers. Windows servers must have PowerShell version 2.0 or later installed.<br /><br /> To discover SQL Server instances and databases, check [supported SQL Server and Windows OS versions and editions](migrate-support-matrix-vmware.md?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) and Windows authentication mechanisms.<br /><br /> To discover ASP.NET web apps running on IIS web server, check [supported Windows OS and IIS versions](migrate-support-matrix-vmware.md?pivots=web-apps-discovery&tabs=businesscase).<br /><br />  To discover Java web apps running on Apache Tomcat web server, check [supported Linux OS and Tomcat versions](migrate-support-matrix-vmware.md?pivots=web-apps-discovery&tabs=businesscase). 
+**Servers** | All Windows and Linux OS versions are supported for discovery of configuration and performance metadata. <br /><br /> For application discovery on servers, all Windows and Linux OS versions are supported. Check the [OS versions supported for agentless dependency analysis](migrate-support-matrix-vmware.md#dependency-analysis-requirements-agentless).<br /><br /> For discovery of installed applications and for agentless dependency analysis, VMware Tools (version 10.2.1 or later) must be installed and running on servers. Windows servers must have PowerShell version 2.0 or later installed.<br /><br /> To discover SQL Server instances and databases, check [supported SQL Server and Windows OS versions and editions](migrate-support-matrix-vmware.md?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) and Windows authentication mechanisms.<br /><br /> To discover ASP.NET web apps running on IIS web server, check [supported Windows OS and IIS versions](migrate-support-matrix-vmware.md?pivots=web-apps-discovery&tabs=businesscase).<br /><br />  To discover Java web apps running on Apache Tomcat web server, check [supported Linux OS and Tomcat versions](migrate-support-matrix-vmware.md?pivots=web-apps-discovery&tabs=businesscase). 
 **SQL Server access** | To discover SQL Server instances and databases, the Windows account, or SQL Server account [requires these permissions](migrate-support-matrix-vmware.md?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) for each SQL Server instance. You can use the [account provisioning utility](../least-privilege-credentials.md) to create custom accounts or use any existing account that is a member of the sysadmin server role for simplicity.
 
 ## Prepare an Azure user account
diff --git a/articles/sentinel/TOC.yml b/articles/sentinel/TOC.yml
@@ -402,6 +402,8 @@
       href: data-connectors/dynatrace-problems.md
     - name: Dynatrace Runtime Vulnerabilities
       href: data-connectors/dynatrace-runtime-vulnerabilities.md
+    - name: ESET Protect Platform (using Azure Functions)
+      href: data-connectors/eset-protect-platform.md
     - name: Elastic Agent (Standalone)
       href: data-connectors/elastic-agent-standalone.md
     - name: Exchange Security Insights On-Premises Collector
diff --git a/articles/sentinel/data-connectors-reference.md b/articles/sentinel/data-connectors-reference.md
@@ -248,6 +248,10 @@ For more information about the codeless connector platform, see [Create a codele
 - [Dynatrace Problems](data-connectors/dynatrace-problems.md)
 - [Dynatrace Runtime Vulnerabilities](data-connectors/dynatrace-runtime-vulnerabilities.md)
 
+## ESET
+
+- [ESET Protect Platform (using Azure Functions)](data-connectors/eset-protect-platform.md)
+
 ## Elastic
 
 - [Elastic Agent (Standalone)](data-connectors/elastic-agent-standalone.md)
diff --git a/articles/sentinel/data-connectors/eset-protect-platform.md b/articles/sentinel/data-connectors/eset-protect-platform.md
@@ -0,0 +1,80 @@
+---
+title: "ESET Protect Platform (using Azure Functions) connector for Microsoft Sentinel"
+description: "Learn how to install the connector ESET Protect Platform (using Azure Functions) to connect your data source to Microsoft Sentinel."
+author: cwatson-cat
+ms.topic: how-to
+ms.date: 01/21/2025
+ms.service: microsoft-sentinel
+ms.author: cwatson
+ms.collection: sentinel-data-connector
+---
+
+# ESET Protect Platform (using Azure Functions) connector for Microsoft Sentinel
+
+The ESET Protect Platform data connector enables users to inject detections data from [ESET Protect Platform](https://www.eset.com/int/business/protect-platform/) using the provided [Integration REST API](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/ESET%20Protect%20Platform/Data%20Connectors). Integration REST API runs as scheduled Azure Function App.
+
+This is autogenerated content. For changes, contact the solution provider.
+
+## Connector attributes
+
+| Connector attribute | Description |
+| --- | --- |
+| **Log Analytics table(s)** | IntegrationTable_CL<br/> |
+| **Data collection rules support** | Not currently supported |
+| **Supported by** | [ESET Enterprise Integrations](https://help.eset.com/eset_connect/en-US/integrations.html) |
+
+## Query samples
+
+**All table records sorted by time**
+
+   ```kusto
+IntegrationTable_CL
+
+   | sort by TimeGenerated desc
+   ```
+
+
+
+## Prerequisites
+
+To integrate with ESET Protect Platform (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/).
+- **Permission to register an application in Microsoft Entra ID**: Sufficient permissions to register an application with your Microsoft Entra tenant are required.
+- **Permission to assign a role to the registered application**: Permission to assign the Monitoring Metrics Publisher role to the registered application in Microsoft Entra ID is required.
+
+
+## Vendor installation instructions
+
+
+> [!NOTE]
+   >  The ESET Protect Platform data connector uses Azure Functions to connect to the ESET Protect Platform via Eset Connect API to pull detections logs into Microsoft Sentinel. This process might result in additional data ingestion costs. See details on the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/).
+
+Step 1 -  Create an API user
+
+Use this [instruction](https://help.eset.com/eset_connect/en-US/create_api_user_account.html) to create an ESET Connect API User account with **Login** and **Password**.
+
+Step 2 -  Create a registered application
+
+Create a Microsoft Entra ID registered application by following the steps in the [Register a new application instruction.](/entra/identity-platform/quickstart-register-app)
+
+Step 3 - Deploy the ESET Protect Platform data connector using the Azure Resource Manager (ARM) template
+
+
+
+1. Click the **Deploy to Azure** button below. 
+
+	[![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-EsetProtectionPlatform-azuredeploy)
+
+2. Select the name of the **Log Analytics workspace** associated with your Microsoft Sentinel. Select the same **Resource Group** as the Resource Group of the Log Analytics workspace.
+
+3. Type the parameters of the registered application in Microsoft Entra ID: **Azure Client ID**, **Azure Client Secret**, **Azure Tenant ID**, **Object ID**. You can find the **Object ID** on Azure Portal by following this path 
+> Microsoft Entra ID -> Manage (on the left-side menu) -> Enterprise applications -> Object ID column (the value next to your registered application name).
+
+4. Provide the ESET Connect API user account **Login** and **Password** obtained in **Step 1**.
+
+
+
+## Next steps
+
+For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/esetresearch1579795941720.eset-protect-platform-solution?tab=Overview) in the Azure Marketplace.
diff --git a/articles/service-connector/includes/code-postgres-me-id.md b/articles/service-connector/includes/code-postgres-me-id.md
@@ -332,7 +332,7 @@ For Ruby, there's not a plugin or library for passwordless connections. You can
     # res = Net::HTTP.get_response(uri, {'X-IDENTITY-HEADER' => ENV['IDENTITY_HEADER'], 'Metadata' => 'true'})  
 
     # For user-assigned identity.
-    # uri = URI(ENV[IDENTITY_ENDPOINT] + '?resource=https://ossrdbms-aad.database.windows.net&api-version=2019-08-01&client-id=' + ENV['AZURE_POSTGRESQL_CLIENTID'])
+    # uri = URI(ENV[IDENTITY_ENDPOINT] + '?resource=https://ossrdbms-aad.database.windows.net&api-version=2019-08-01&client_id=' + ENV['AZURE_POSTGRESQL_CLIENTID'])
     # res = Net::HTTP.get_response(uri, {'X-IDENTITY-HEADER' => ENV['IDENTITY_HEADER'], 'Metadata' => 'true'})  
     
     # For service principal
diff --git a/articles/service-connector/tutorial-python-aks-openai-workload-identity.md b/articles/service-connector/tutorial-python-aks-openai-workload-identity.md
@@ -9,7 +9,7 @@ ms.service: service-connector
 ms.custom: devx-track-python, build-2024, devx-track-azurecli
 ms.collection: ce-skilling-ai-copilot
 ms.topic: tutorial
-ms.date: 05/07/2024
+ms.date: 01/22/2025
 ---
 
 # Tutorial: Connect to Azure OpenAI Service in AKS using Workload Identity (preview)
@@ -148,19 +148,26 @@ Once the connection has been created, you can view its details in the **Service
 
 ### [Azure CLI](#tab/azure-cli)
 
-Use the Azure CLI command to create a service connection to the Azure OpenAI service, providing the following information:
-
-* **Source compute service resource group name:** the resource group name of the AKS cluster.
-* **AKS cluster name:** the name of your AKS cluster that connects to the target service.
-* **Target service resource group name:** the resource group name of the Azure OpenAI service.
-* **OpenAI service name:** the Azure OpenAI service that is connected.
-* **User-assigned identity resource ID:** the resource ID of the user-assigned identity used to create the workload identity.
+Create a service connection in AKS by running the [az aks connection create](/cli/azure/aks/connection/create#az-aks-connection-create-cognitiveservices) command in the Azure CLI. 
 
 ```azurecli
 az aks connection create cognitiveservices \
    --workload-identity <user-identity-resource-id>
 ```
 
+When using the above command, Service Connector prompts you to specify the AKS resource group, AKS cluster name, target service resource group, cognitive service account name, and user-assigned identity resource ID step by step.
+
+Alternatively, you can provide the complete command directly:
+
+```azurecli
+az aks connection create cognitiveservices \
+   --workload-identity <user-identity-resource-id> \
+   --resource-group <aks-cluster-resource-group> \
+   --name <aks-cluster-name> \
+   --target-resource-group <target-cognitive-services-resource-group> \
+   --account <target-cognitive-services-account>
+```
+
 ---
 
 ## Clone sample application
