Skip to content

Commit 765c1e2

Browse files
authored
Merge pull request #93274 from MGoedtel/UpdateAzMonGateway1024
updated HRW config section
2 parents ae69372 + 36dcf98 commit 765c1e2

File tree

1 file changed

+4
-43
lines changed

1 file changed

+4
-43
lines changed

articles/azure-monitor/platform/gateway.md

Lines changed: 4 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: log-analytics
1111
ms.workload: na
1212
ms.tgt_pltfrm: na
1313
ms.topic: conceptual
14-
ms.date: 08/12/2019
14+
ms.date: 10/24/2019
1515
ms.author: magoedte
1616
---
1717

@@ -295,50 +295,11 @@ To configure specific servers or groups to use the Log Analytics gateway server:
295295

296296
### Configure for Automation Hybrid Runbook Workers
297297

298-
If you have Automation Hybrid Runbook Workers in your environment, follow these steps for manual, temporary workarounds to configure OMS Gateway to support the workers.
298+
If you have Automation Hybrid Runbook Workers in your environment, follow these steps to configure the gateway to support the workers.
299299

300-
To follow the steps in this section, you need to know the Azure region where the Automation account resides. To find that location:
300+
Refer to the [Configure your network](../../automation/automation-hybrid-runbook-worker.md#network-planning) section of the Automation documentation to find the URL for each region.
301301

302-
1. Sign in to the [Azure portal](https://portal.azure.com/).
303-
1. Select the Azure Automation service.
304-
1. Select the appropriate Azure Automation account.
305-
1. View its region under **Location**.
306-
307-
![Screenshot of the Automation account location in the Azure portal](./media/gateway/location.png)
308-
309-
Use the following tables to identify the URL for each location.
310-
311-
**Job Runtime Data service URLs**
312-
313-
| **Location** | **URL** |
314-
| --- | --- |
315-
| North Central US |ncus-jobruntimedata-prod-su1.azure-automation.net |
316-
| West Europe |we-jobruntimedata-prod-su1.azure-automation.net |
317-
| South Central US |scus-jobruntimedata-prod-su1.azure-automation.net |
318-
| East US 2 |eus2-jobruntimedata-prod-su1.azure-automation.net |
319-
| Central Canada |cc-jobruntimedata-prod-su1.azure-automation.net |
320-
| North Europe |ne-jobruntimedata-prod-su1.azure-automation.net |
321-
| South East Asia |sea-jobruntimedata-prod-su1.azure-automation.net |
322-
| Central India |cid-jobruntimedata-prod-su1.azure-automation.net |
323-
| Japan |jpe-jobruntimedata-prod-su1.azure-automation.net |
324-
| Australia |ase-jobruntimedata-prod-su1.azure-automation.net |
325-
326-
**Agent service URLs**
327-
328-
| **Location** | **URL** |
329-
| --- | --- |
330-
| North Central US |ncus-agentservice-prod-1.azure-automation.net |
331-
| West Europe |we-agentservice-prod-1.azure-automation.net |
332-
| South Central US |scus-agentservice-prod-1.azure-automation.net |
333-
| East US 2 |eus2-agentservice-prod-1.azure-automation.net |
334-
| Central Canada |cc-agentservice-prod-1.azure-automation.net |
335-
| North Europe |ne-agentservice-prod-1.azure-automation.net |
336-
| South East Asia |sea-agentservice-prod-1.azure-automation.net |
337-
| Central India |cid-agentservice-prod-1.azure-automation.net |
338-
| Japan |jpe-agentservice-prod-1.azure-automation.net |
339-
| Australia |ase-agentservice-prod-1.azure-automation.net |
340-
341-
If your computer is registered as a Hybrid Runbook Worker automatically, use the Update Management solution to manage the patch. Follow these steps:
302+
If your computer is registered as a Hybrid Runbook Worker automatically, for example if the Update Management solution is enabled for one or more VMs, follow these steps:
342303

343304
1. Add the Job Runtime Data service URLs to the Allowed Host list on the Log Analytics gateway. For example:
344305
`Add-OMSGatewayAllowedHost we-jobruntimedata-prod-su1.azure-automation.net`

0 commit comments

Comments
 (0)