Below are the quick and dirty details you need to connect your Windows servers to OMS hosted in Microsoft Azure Government (MAG). Any server with internet access can report to an OMS workspace (including but not limited to servers located on-premises, in the Azure Commercial cloud, hosted by other cloud providers, etc.).
- Azure Extension – Note: Azure VMs only, VM must be in the same subscription as the OMS Workspace. In portal.azure.us goto Log Analytics –> Your Workspace –> Workspace Data Sources –> Virtual Machines –> Connect the desired VM (click on the VM, in the new blade click connect). The extension installs the full OMS agent on your VM. For details see https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-azure-vm-extension
- OMS Agent (MSI) – the MSI can be installed interactively or via command line. Download the agent from the OMS Portal (settings –> connected sources –> Windows Servers). For full details, see https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-windows-agents#download-the-agent-setup-file-from-oms
- If installing the agent interactively, be sure you specify the cloud as Azure Government
- If installing the agent via the command line, you’ll need to use the “OPINSIGHTS_WORKSPACE_AZURE_CLOUD_TYPE=1 parameter to point to Azure Government. For example:
- run: extract MMASetup-AMD64.exe
- then run: setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_AZURE_CLOUD_TYPE=1 OPINSIGHTS_WORKSPACE_ID=yourid OPINSIGHTS_WORKSPACE_KEY=yourkey AcceptEndUserLicenseAgreement=1
Adding an OMS Workspace to an Existing Installation
To update an existing OMS or SCOM agent to point to a new/additional OMS workspace you can either manually configure the new workspace via the GUI or leverage PowerShell.
2. Programmatically via PowerShell. Note: the 1 at the end of the AddCloudWorkspace cmdlet indicates the workspace is in Azure Government.
$mma = New-Object -ComObject ‘AgentConfigManager.MgmtSvcCfg’
$mma.AddCloudWorkspace($workspaceId, $workspaceKey, 1)