Azure Monitor

The Azure Monitor page in MSPControl is used to manage Azure Monitor workspaces connected to the current organization. This section gives administrators a central place to store workspace details, maintain monitoring-related configuration, and review whether Microsoft Sentinel watchlist synchronization is enabled for a workspace.

This page is especially useful in Azure-connected environments where monitoring data, analytics, or security-related telemetry must be linked to a specific Log Analytics workspace. Instead of keeping those settings outside the platform, MSPControl allows administrators to manage the workspace connection directly in the Azure section.

Table of Contents

• Azure Monitor Overview
• Azure Monitor List Page
• Azure Monitor Table Columns
• Create or Edit Workspace
• Workspace Fields
• Data Collection Rules
• Page Actions
• Best Practices

Azure Monitor Overview

The Azure Monitor section acts as a workspace management page. It allows administrators to see which Azure Monitor workspace records already exist, create a new one, and update monitoring-related configuration for a selected workspace.

Based on the screen layout, this page is centered around Log Analytics or Azure Monitor workspace connectivity rather than general dashboarding. The presence of fields such as Workspace ID, Primary key, and Data Collection Rules indicates that this page is intended for configuration and integration, not only for reporting.

Azure Monitor List Page

The main Azure Monitor page displays configured workspace records in a table. This list helps administrators quickly review the current workspaces and confirm whether Sentinel watchlist synchronization is enabled for each entry.

Azure Monitor Page Controls

1. Create opens the workspace form where a new Azure Monitor workspace record can be added.
2. Category Filter allows administrators to narrow the visible list using the available dropdown options.
3. Search helps find a workspace by name, workspace ID, or other searchable value.
4. Column Visibility allows administrators to choose which columns remain visible in the table.
5. Page Size Selector controls how many workspace rows are shown at one time.

Azure Monitor Table Columns

1. Name shows the workspace record name inside MSPControl.
2. Workspace ID shows the Azure Monitor workspace identifier.
3. Sync Sentinel WatchLists shows whether watchlist synchronization is enabled for the workspace.
4. Actions provides row-level actions. In the screenshot provided, a delete action is visible.

This list is useful for confirming which workspaces are already configured and whether they are set up for additional Sentinel-related synchronization.

Create or Edit Workspace

When administrators create a new workspace or open an existing one, MSPControl shows a dedicated Workspaces page. This page contains the main workspace connection settings and a nested section for Data Collection Rules.

This means the workspace record in MSPControl is not only a label. It serves as a connection point for monitoring-related Azure configuration and optional Sentinel watchlist synchronization.

Workspace Fields

1. Name defines the visible name of the workspace record inside MSPControl.
2. Workspace ID defines the Azure Monitor workspace identifier. This is one of the main values required to connect the workspace correctly.
3. Primary key stores the workspace primary key. The eye icon indicates that this value can be shown or hidden for secure handling.
4. Sync Sentinel WatchLists controls whether Microsoft Sentinel watchlist synchronization should be enabled for this workspace.

These fields form the core workspace configuration. The Workspace ID and Primary key are especially important because they represent the actual connection details used by the monitoring integration.

Data Collection Rules

The Data Collection Rules section is used to manage data collection rule records related to the workspace. In the screenshot provided, the section contains a button for creating a new data collection rule and a table for displaying existing rule entries.

At the moment shown in the screenshot, no records exist yet. The section still reveals the intended structure of the feature and shows which details are expected for each rule.

Data Collection Rules Controls

1. New Data Collection Rule starts the workflow for adding a new rule to the workspace.

Data Collection Rules Table Columns

1. Name shows the rule name.
2. Resource Group shows the Azure resource group linked to the rule.
3. Data Sources shows the data sources defined for the rule.
4. Location shows the Azure location for the rule.
5. Actions provides row-level actions for the rule entry.

This section suggests that MSPControl is prepared to manage rule-based ingestion or monitoring scope within the workspace context, even if the current example does not yet contain configured rules.

Why Sentinel WatchList Sync Matters

The Sync Sentinel WatchLists option is important because it indicates that the workspace can also participate in Microsoft Sentinel-related workflows. This makes the Azure Monitor workspace relevant not only for general monitoring and analytics, but also for security and watchlist-based processes when the organization uses Sentinel.

Keeping this option on the workspace itself also makes administration easier, because administrators can see at a glance which workspaces are being used only for monitoring and which ones are additionally tied to Sentinel watchlist synchronization.

Page Actions

1. Cancel closes the workspace page without saving the current changes.
2. Save Changes and Exit saves the workspace configuration and returns to the previous page.
3. Save Changes saves the current configuration without leaving the page.

Because workspace connection settings are sensitive and important for monitoring integration, administrators should verify the entered values before saving.

How Azure Monitor Fits into MSPControl

The Azure Monitor page gives MSPControl a dedicated place for workspace-level monitoring configuration. Instead of storing workspace credentials and Sentinel-related settings outside the platform, administrators can maintain them directly in the Azure section for the hosted organization.

This makes the page useful as both a configuration record and an operational reference point. It connects the organization to the Azure Monitor workspace and provides a place to expand into additional data collection rule management over time.

Best Practices

• Use a clear Name for each workspace record so administrators can easily identify its purpose inside MSPControl.
• Verify the Workspace ID carefully before saving, because it is one of the main identifiers used for the Azure Monitor connection.
• Handle the Primary key carefully, since it is sensitive connection data.
• Enable Sync Sentinel WatchLists only when the workspace is intended to participate in Sentinel-related processes.
• Use the list page regularly to review which workspaces are configured and whether they are aligned with the intended monitoring design.
• Add Data Collection Rules only when there is a clear monitoring or ingestion need for the workspace.
• Review empty rule sections as a configuration reminder, not as an error, when the workspace has not yet been assigned any data collection rules.
• Save workspace changes only after confirming that all connection values and monitoring options are correct for the hosted organization.