Last reviewed: November 22, 2026 | For beginners, instructors, and first-time SIEM learners | Microsoft Azure • Microsoft Sentinel • Microsoft Defender • Azure Activity • KQL
Microsoft Sentinel is now operated primarily through the Microsoft Defender portal. You still use Microsoft Azure to create the Log Analytics workspace and configure Azure resources, but https://security.microsoft.com/ is the main web address to bookmark for the Sentinel security-operations experience.
This tutorial takes you along one straightforward learning path: create a Sentinel workspace, open it in Microsoft Defender, install the Azure Activity solution, route actual Azure management events to the workspace, and verify ingestion with one short KQL exercise at the very end. It follows the newer Defender layout and uses a supported Azure Monitor diagnostic setting for log delivery—without adding an Azure Policy assignment for the same export.
The essential distinction: Microsoft Sentinel is the cloud-native SIEM/SOAR service. Microsoft Defender is the unified portal and a family of security products. Defender Home is a shared landing page, not a separate Sentinel account or a replacement for the Sentinel service. You can use Sentinel in the Defender portal without a Defender XDR or Microsoft 365 E5 license; normal Sentinel/Azure charges can still apply. Microsoft Learn: Sentinel in Defender portal
1. Know the two official portals
| Portal | URL | When to use it |
|---|---|---|
| Microsoft Azure portal | portal.azure.com | Choose a subscription; create a Log Analytics workspace; enable Sentinel; configure subscription Activity Log export; open Logs for workspace-specific queries. |
| Microsoft Defender portal | security.microsoft.com | Use unified Home, find Sentinel’s Content hub, explore connectors, manage incidents, analytics, hunting, and security operations. |
Beginner setup route: Azure subscription → Log Analytics workspace → Enable Microsoft Sentinel → Microsoft Defender Home → Install Azure Activity solution → Export Azure Activity to the workspace → Verify with KQL.
Microsoft has announced that after March 31, 2027, Sentinel will no longer be supported in the Azure portal and will be available through the Defender portal. This article uses Azure today for the resource configuration and workspace-specific Logs experience available in November 2026. Official portal guidance
2. Prerequisites and sample lab values
You need an active Azure subscription, an identity in the correct Microsoft Entra tenant, and permissions to deploy Azure resources and configure subscription diagnostic settings. Microsoft documents subscription Contributor permissions to enable Sentinel, as well as Microsoft Sentinel Contributor for managing Content Hub solutions at the workspace’s resource-group scope. For personal labs, a suitably authorized subscription owner can perform the required Azure resource-management actions. Official onboarding requirements
Use your own values. The table below preserves the names used in the verified hands-on walkthrough:
| Setting | Worked example |
|---|---|
| Azure subscription | Pay-As-You-Go - new |
| Resource group | senti |
| Log Analytics workspace | Rajesh |
| Region | West US 3 (westus3) |
| Sentinel operating URL | https://security.microsoft.com/ |
A first learning lab does not require an ISOC transition, an ISOC role import, activating Unified RBAC, configuring UEBA, or purchasing Defender XDR. These are separate administration or advanced-security topics, not steps in the baseline quickstart.
3. Step 1 — Open Azure and verify the subscription
- Open https://portal.azure.com/ and sign in.
- In the top Search resources, services, and docs box, type Subscriptions.
- Open Subscriptions and select the subscription you will use.
- If your account has access to multiple directories, use the directory/subscription selector to ensure you’re working in the Microsoft Entra tenant containing that subscription.
You should now have: an active subscription selected for the Sentinel lab.
4. Step 2 — Create a Log Analytics workspace
- In Azure’s top search box, type Microsoft Sentinel and open the service.
- Select Create.
- Select Create a new workspace.
- Choose your subscription, a new or existing resource group, and an available workspace name and region.
- Select Review + Create, then Create.
For a new classroom environment, example names are rg-sentinel-training and law-sentinel-training-01. If following the worked example, its workspace is named Rajesh in resource group senti.
You should now have: a Log Analytics workspace. A workspace alone is not yet Sentinel-enabled.
5. Step 3 — Enable Microsoft Sentinel on that workspace
- Return to Azure Portal → Microsoft Sentinel.
- Select Create (the action to add Sentinel to a workspace).
- Select the Log Analytics workspace created in Step 2.
- Select Add.
You should now have: Microsoft Sentinel enabled on the workspace. Microsoft automatically onboards many eligible new customers to the Defender portal, so a separate manual connection is not necessarily required. Microsoft’s current onboarding quickstart
6. Step 4 — Reach Microsoft Sentinel in Microsoft Defender
- Open https://security.microsoft.com/.
- Sign in to the same Microsoft Entra tenant and with an account permitted to access the Sentinel workspace.
- Open Home from the left navigation. This is the Microsoft Defender Home dashboard; it may show a “Microsoft Sentinel is here” banner and Sentinel-related cards.
- Expand Microsoft Sentinel in the left navigation to see its dedicated menu, including Content management, Threat management, and Configuration.
- To confirm the workspace connection, go to Setup & configuration → Settings → Microsoft Sentinel → SIEM workspaces. The Microsoft documentation also refers to System → Settings → Microsoft Sentinel → Workspaces in some layouts.
- Confirm that the workspace appears as Connected, and Primary if it is the tenant’s primary workspace.
You should now have: access to the Microsoft Sentinel experience in Defender, using a connected Log Analytics workspace.
Which page is the “Microsoft Sentinel main page”?
Defender Home is the new unified landing page for the whole security portal. It can include Sentinel cards alongside other Defender signals. Microsoft Sentinel remains a separate left-hand navigation section containing its features. A dedicated Sentinel Overview may be accessible in supported portal layouts, but it is not the same thing as the general Defender Home page.
7. Step 5 — Install Azure Activity in Sentinel Content Hub
The Azure Activity solution is an excellent first teaching example. It supplies Sentinel content associated with Azure subscription management activity. Installing the solution does not, by itself, switch on log export. That is the next step.
- In Defender, expand Microsoft Sentinel → Content management → Content hub.
- Search for Azure Activity and select the Azure Activity solution (the parent solution, not an individual rule or query beneath it).
- Select Install from its details pane, or use Install/Update for the selected solution in list view, whichever the interface shows.
- Finish the installation for your existing Sentinel workspace.
- Check that the Azure Activity solution’s status reads Installed.
You should now have: the Azure Activity solution installed in your workspace, with its associated content available. Microsoft’s Content Hub instructions
8. Step 6 — Find the Azure Activity connector in the new Defender layout
- In Defender, expand Setup & configuration.
- Select Data & connectors. In some documented layouts this appears under Data management → Data & connectors.
- Open the Connectors tab.
- From the connector-type dropdown, select Classic connectors – Microsoft Sentinel.
- Locate Azure Activity, open its … menu, and select Open connector page.
- Review the Azure Activity connector details and its data-ingestion status.
You should now have: the Azure Activity Connector details page open. This page explains the connector and shows whether logs have been received. Microsoft’s November 2026 navigation reference
For this short learning lab, the next step uses Azure Monitor’s supported diagnostic-settings interface directly. The connector page may also expose an Azure Policy Assignment wizard for managed deployment. That is an alternative configuration mechanism, not another required step to perform after creating the same export manually.
9. Step 7 — Export Azure Activity logs to Log Analytics (one method only)
Azure Activity logs record management actions such as creating and deleting resource groups, deployments, and configuration changes. Azure Monitor collects those events at the subscription level. A subscription diagnostic setting forwards selected categories into the workspace’s AzureActivity table. Azure Monitor Activity Log documentation
- Open Azure Portal in a separate browser tab.
- In the top search box, open Monitor.
- Select Activity log and make sure the correct subscription is selected.
- Choose Export Activity Logs to open the subscription’s Diagnostic settings page.
- Review the existing settings. Use an existing setting if it already sends the desired categories to your Sentinel workspace; otherwise select + Add diagnostic setting.
- Give the new setting a descriptive name, for example
subscription-to-sentinel. - Under Logs / Categories, select Administrative at minimum. This is sufficient for demonstrating Azure resource-management events.
- Under Destination details, check Send to Log Analytics workspace.
- Select the destination subscription and your Sentinel-enabled Log Analytics workspace (for the worked example,
Rajesh). - Select Save.
You should now have: one subscription-level diagnostic setting that forwards Administrative events to the Sentinel workspace. In the completed example, the existing setting was called subscriptionToLa and pointed to Rajesh.
Do not add another diagnostic setting for the same category and same Log Analytics destination. A single correct export is enough; creating an equivalent second export is unnecessary. Allow for Azure Monitor’s normal delivery and ingestion latency before demonstrating the query to a class. Official diagnostic-settings guide
10. Step 8 — Understand the current operating navigation
Return to Microsoft Defender Home for your daily security-operations interface.
| Goal | Microsoft Defender navigation (November 2026) |
|---|---|
| Home / unified dashboard | Home |
| Installed Sentinel solutions | Microsoft Sentinel → Content management → Content hub |
| Azure Activity connector | Setup & configuration → Data & connectors → Connectors → Classic connectors – Microsoft Sentinel |
| Sentinel workspaces | Setup & configuration → Settings → Microsoft Sentinel → SIEM workspaces |
| Security incidents | Investigation & response → Incidents & alerts → Incidents |
| Analytics rules | Investigation & response → Detection → Analytics |
| Advanced security hunting | Investigation & response → Hunting → Advanced hunting |
| Sentinel workbooks | Dashboards & reports → Workbooks, or Microsoft Sentinel → Threat management → Workbooks when displayed |
These names follow the Defender layout used in November 2026; some groups may be organized differently by portal experience. The feature name is the most reliable landmark. Official feature mapping
Use the correct KQL editor for your first Azure Activity test
Do your initial AzureActivity exercise in Azure Portal → Log Analytics workspaces → [your workspace] → Logs, not in an unscoped Defender Advanced hunting tab.
Both environments use KQL, but they are not interchangeable query contexts. Microsoft Defender Advanced hunting can query supported Sentinel workspace tables when that data is present and accessible in its unified schema. Opening Advanced hunting alone does not establish that AzureActivity is available to that editor. The workspace’s own Logs view is the direct, deterministic place to verify the subscription Activity Log export configured in Step 7. Microsoft Learn: Advanced hunting with Sentinel
For example, the first successful classroom exercise should validate real data in a Sentinel-enabled workspace before students move on to advanced cross-product hunting.
11. Costs for a classroom lab
Microsoft documents an introductory 31-day trial with up to 10 GB/day of eligible Analytics log ingestion for qualifying Sentinel workspaces. The trial does not make every Azure service, automation action, or other security capability free. Costs depend on your subscription and features. Review Azure Cost Management before adding more data sources. Microsoft Sentinel pricing and trial
Azure Monitor documents that exporting subscription Activity Log data to a Log Analytics workspace has specific no-ingestion-charge treatment, subject to its retention and service terms; don’t assume every other Sentinel data connector has the same pricing. Azure Monitor Activity Log
12. Official Microsoft references (checked November 22, 2026)
The steps above are based on official Microsoft Learn articles, rather than older screenshots from the pre-integration Sentinel Azure interface:
- Onboard Microsoft Sentinel to a Log Analytics workspace — Azure deployment, Content Hub, and Azure Activity onboarding.
- Microsoft Sentinel in the Microsoft Defender portal — current portal experience and navigation; updated November 17, 2026.
- Connect Microsoft Sentinel to the Microsoft Defender portal — connection and primary workspace.
- Discover and manage out-of-the-box content — installing solutions in Content Hub.
- Connect data sources using data connectors — connector access and configuration.
- Activity log in Azure Monitor — exporting subscription activity logs into
AzureActivity. - Diagnostic settings in Azure Monitor — supported log destinations and configuration.
- Advanced hunting with Microsoft Sentinel data — unified hunting schema and access; updated November 17, 2026.
- Microsoft Sentinel pricing and billing — current trial and charging model.
Final 2–3 Minute Hello World Lab — Confirm Microsoft Sentinel Is Ready
Goal: Run one query that prints a greeting and proves your Sentinel-enabled Log Analytics workspace contains real Azure Activity events. This lab assumes the export from Step 7 has begun sending records.
- Open Azure Portal → Log Analytics workspaces → your workspace → Logs (worked example:
Rajesh). - Select KQL mode if the editor offers a mode choice. Set the time selector to Last 7 days.
- Paste the following query, select Run, and read the result row.
AzureActivity
| where TimeGenerated > ago(7d)
| summarize
Events = count(),
LastEventUTC = max(TimeGenerated)
| extend
HelloWorld = "Hello World! Microsoft Sentinel is ready",
Verification = iff(
Events > 0,
"PASS: KQL works and Azure Activity data is present",
"KQL works, but no Azure Activity events in the last 7 days"
),
CheckedAtUTC = now()
| project HelloWorld, Verification, Events, LastEventUTC, CheckedAtUTC
Expected successful output: One row with HelloWorld = Hello World! Microsoft Sentinel is ready, Verification starting with PASS, and Events greater than zero. LastEventUTC shows the timestamp of the latest matching activity record.
What this proves: KQL executed against the intended Sentinel-enabled Log Analytics workspace and actual Azure Activity records were ingested. Your foundation is ready for learning detections, incidents, hunting, and automation.