Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Commit

Permalink
Merge branch 'scommidocs' of https://github.com/Azure/FTALive-Sessions
Browse files Browse the repository at this point in the history
…into scommidocs
  • Loading branch information
josefehse committed Apr 16, 2024
2 parents 8107631 + 53d5ac7 commit d1cd4ef
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions content/management/scom-mi/agents.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,16 @@ Azure Monitor SCOM Managed Instance provides a cloud-based alternative for Opera
The following are the supported monitoring scenarios:

- Azure Windows VMs that have Line of sight connectivity to the Management Server
- Azure VMs with no Line of sight connectivity (must use managed Gateway)
- On-premise Arc-enabled VMs that have Line of sight connectivity to Management Server.
- On-premises agents with no Line of sight connectivity (must use managed Gateway) to Azure
- On-premise Windows & Linux Arc-enabled VMs that have Line of sight connectivity to Management Server.
- On-premise Windows & Linux agent VMs that have Line of sight connectivity to Management Server.
- On-premises Windows agents with no Line of sight connectivity (must use managed Gateway) to Azure

Note:

- Linux VMs in Azure and Arc-enabled Linux VMs are not currently supported. However, they can be managed via the Arc-enabled gateway servers.
- Linux VMs in Azure and Linux VMs that sit behind a gateway are not currently supported.
- Agent multi-homing isn't supported to multiple SCOM Managed Instances. However, it can have a multi-home configuration for on-premises System Center Operations Manager and a SCOM Managed Instance.
- Agents that are directly connected to the SCOM MI need to be able to reach westus.workloadnexus.azure.com on port 443.
- .NET 4.7.2 and TLS 1.2 IS required for agent install.
- Agents that are directly connected to the SCOM MI need to be able to reach <region>.workloadnexus.azure.com on port 443.
- .NET 4.7.2 and TLS 1.2 is required for agent install.

## Managed Gateways

Expand All @@ -32,7 +32,7 @@ Managed Gateways need to be Arc-enabled with the Gateway extension installed, it
Note:

- Currently, multi-homing for gateway servers isn't supported.
- Arc-enabled Gateways require line of sight to westus.workloadnexus.azure.com on port 443.
- Arc-enabled Gateways require line of sight to <region>.workloadnexus.azure.com on port 443.
- Initial authentication is performed by a managed identity, then certificates are used to manage Managed Gateways by Microsoft.

#### [Previous](setup.md) | [Home](readme.md) | [Next](newfeatures.md)

0 comments on commit d1cd4ef

Please sign in to comment.