You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scenarios to enable and configure antimalware, including monitoring for Azure Cloud Services and Virtual Machines, are discussed in this section.
106
106
107
107
### Virtual machines - enable and configure antimalware
108
108
109
-
#### Deployment While creating a VM using the Azure portal
109
+
#### Deployment while creating a VM using the Azure portal
110
110
111
111
Follow these steps to enable and configure Microsoft Antimalware for Azure Virtual Machines using the Azure portal while provisioning a Virtual Machine:
112
112
@@ -154,7 +154,7 @@ To enable and configure the Microsoft Antimalware service using Visual Studio:
154
154
> [!NOTE]
155
155
> The Visual Studio Virtual Machines configuration for Antimalware supports only JSON format configuration. For more information about sample configurations, see [Code samples to enable and configure Microsoft Antimalware for Azure](antimalware-code-samples.md).
156
156
157
-
#### Deployment Using PowerShell cmdlets
157
+
#### Deployment using PowerShell cmdlets
158
158
159
159
An Azure application or service can enable and configure Microsoft Antimalware for Azure Virtual Machines using PowerShell cmdlets.
160
160
@@ -166,7 +166,7 @@ To enable and configure Microsoft Antimalware using PowerShell cmdlets:
166
166
> [!NOTE]
167
167
>The Azure Virtual Machines configuration for Antimalware supports only JSON format configuration. For more information about sample configurations, see [Code samples to enable and configure Microsoft Antimalware for Azure](antimalware-code-samples.md).
168
168
169
-
### Enable and Configure Antimalware Using PowerShell cmdlets
169
+
### Enable and configure antimalware using PowerShell cmdlets
170
170
171
171
An Azure application or service can enable and configure Microsoft Antimalware for Azure Cloud Services using PowerShell cmdlets. Microsoft Antimalware is installed in a disabled state in the Cloud Services platform and requires an action by an Azure application to enable it.
172
172
@@ -177,7 +177,7 @@ To enable and configure Microsoft Antimalware using PowerShell cmdlets:
177
177
178
178
For more information about sample PowerShell commands, see [Code samples to enable and configure Microsoft Antimalware for Azure](antimalware-code-samples.md).
179
179
180
-
### Cloud Services and Virtual Machines - Configuration Using PowerShell cmdlets
180
+
### Cloud Services and Virtual Machines - configuration using PowerShell cmdlets
181
181
182
182
An Azure application or service can retrieve the Microsoft Antimalware configuration for Cloud Services and Virtual Machines using PowerShell cmdlets.
183
183
@@ -189,7 +189,7 @@ To retrieve the Microsoft Antimalware configuration using PowerShell cmdlets:
189
189
190
190
## Samples
191
191
192
-
### Remove Antimalware Configuration Using PowerShell cmdlets
192
+
### Remove antimalware configuration using PowerShell cmdlets
193
193
194
194
An Azure application or service can completely remove Microsoft Antimalware protection by uninstalling the relevant extensions from your Cloud Services or Virtual Machines. This process removes both the antimalware protection and associated monitoring settings, completely discontinuing malware protection and event collection for the specified resources.
195
195
@@ -211,7 +211,7 @@ Antimalware events are collected from the Windows event system logs to your Azur
211
211
212
212

213
213
214
-
### Enable and configure Antimalware using PowerShell cmdlets for Azure Resource Manager VMs
214
+
### Enable and configure antimalware using PowerShell cmdlets for Azure Resource Manager VMs
215
215
216
216
To enable and configure Microsoft Antimalware for Azure Resource Manager VMs using PowerShell cmdlets:
217
217
@@ -223,7 +223,7 @@ The following code samples are available:
223
223
-[Deploy Microsoft Antimalware on ARM template VMs](antimalware-code-samples.md#deploy-microsoft-antimalware-on-azure-resource-manager-vms)
224
224
-[Add Microsoft Antimalware to Azure Service Fabric Clusters](antimalware-code-samples.md#add-microsoft-antimalware-to-azure-service-fabric-clusters)
225
225
226
-
### Enable and configure Antimalware to Azure Cloud Service Extended Support (CS-ES) using PowerShell cmdlets
226
+
### Enable and configure antimalware to Azure Cloud Service Extended Support (CS-ES) using PowerShell cmdlets
227
227
228
228
To enable and configure Microsoft Antimalware using PowerShell cmdlets:
229
229
@@ -234,7 +234,7 @@ The following code sample is available:
234
234
235
235
-[Add Microsoft Antimalware to Azure Cloud Service using Extended Support(CS-ES)](antimalware-code-samples.md#add-microsoft-antimalware-to-azure-cloud-service-using-extended-support)
236
236
237
-
### Enable and configure Antimalware using PowerShell cmdlets for Azure Arc-enabled servers
237
+
### Enable and configure antimalware using PowerShell cmdlets for Azure Arc-enabled servers
238
238
239
239
To enable and configure Microsoft Antimalware for Azure Arc-enabled servers using PowerShell cmdlets:
Copy file name to clipboardExpand all lines: articles/security/fundamentals/operational-best-practices.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,13 @@ ms.author: mbaldwin
14
14
---
15
15
16
16
# Azure Operational Security best practices
17
+
17
18
This article provides a set of operational best practices for protecting your data, applications, and other assets in Azure.
18
19
19
20
The best practices are based on a consensus of opinion, and they work with current Azure platform capabilities and feature sets. Opinions and technologies change over time and this article is updated on a regular basis to reflect those changes.
20
21
21
22
## Define and deploy strong operational security practices
23
+
22
24
Azure operational security refers to the services, controls, and features available to users for protecting their data, applications, and other assets in Azure. Azure operational security is built on a framework that incorporates the knowledge gained through capabilities that are unique to Microsoft, including the [Security Development Lifecycle (SDL)](https://www.microsoft.com/sdl), the [Microsoft Security Response Center](https://www.microsoft.com/msrc?rtc=1) program, and deep awareness of the cybersecurity threat landscape.
Copy file name to clipboardExpand all lines: articles/security/fundamentals/operational-overview.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: msmbaldwin
7
7
ms.service: security
8
8
ms.subservice: security-fundamentals
9
9
ms.topic: article
10
-
ms.date: 12/03/2025
10
+
ms.date: 01/12/2026
11
11
ms.author: mbaldwin
12
12
13
13
---
@@ -98,7 +98,7 @@ You can also use monitoring data to gain deep insights about your application. T
98
98
99
99
Azure Monitor includes the following components.
100
100
101
-
### Azure Activity Log
101
+
### Azure activity log
102
102
103
103
The [Azure Activity Log](/azure/azure-monitor/essentials/platform-logs-overview) provides insight into the operations that were performed on resources in your subscription. It was previously known as “Audit Log” or “Operational Log,” because it reports control-plane events for your subscriptions.
104
104
@@ -114,7 +114,7 @@ Diagnostic logs differ from the [Activity Log](/azure/azure-monitor/essentials/p
114
114
115
115
Azure Monitor provides telemetry that gives you visibility into the performance and health of your workloads on Azure. The most important type of Azure telemetry data is the [metrics](/azure/azure-monitor/data-platform) (also called performance counters) emitted by most Azure resources. Azure Monitor provides several ways to configure and consume these metrics for monitoring and troubleshooting.
116
116
117
-
### Azure Diagnostics
117
+
### Azure diagnostics
118
118
119
119
Azure Diagnostics enables the collection of diagnostic data on a deployed application. You can use the Diagnostics extension from various sources. Currently supported are [Azure cloud service roles](/visualstudio/azure/vs-azure-tools-configure-roles-for-cloud-service), [Azure virtual machines](/visualstudio/azure/vs-azure-tools-configure-roles-for-cloud-service) running Microsoft Windows, and [Azure Service Fabric](/azure/azure-monitor/agents/diagnostics-extension-overview).
120
120
@@ -144,13 +144,13 @@ Network Watcher currently has the following capabilities:
144
144
145
145
For more information, see [Configure Network Watcher](../../network-watcher/network-watcher-create.md).
146
146
147
-
## Cloud Service Provider Access Transparency
147
+
## Cloud service provider access transparency
148
148
149
149
[Customer Lockbox for Microsoft Azure](customer-lockbox-overview.md) is a service integrated into Azure portal that gives you explicit control in the rare instance when a Microsoft Support Engineer may need access to your data to resolve an issue.
150
150
There are very few instances, such as a debugging remote access issue, where a Microsoft Support Engineer requires elevated permissions to resolve this issue. In such cases, Microsoft engineers use just-in-time access service that provides limited, time-bound authorization with access limited to the service.
151
151
While Microsoft has always obtained customer consent for access, Customer Lockbox now gives you the ability to review and approve or deny such requests from the Azure portal. Microsoft support engineers will not be granted access until you approve the request.
152
152
153
-
## Standardized and Compliant Deployments
153
+
## Standardized and compliant deployments
154
154
155
155
[Azure Blueprints](../../governance/blueprints/overview.md) enable cloud architects and central information technology groups to define a repeatable set of Azure resources that implement and adhere to an organization's standards, patterns, and requirements.
156
156
This makes it possible for DevOps teams to rapidly build and stand up new environments and trust that they're building them with infrastructure that maintains organizational compliance.
Copy file name to clipboardExpand all lines: articles/security/fundamentals/operational-security.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,16 @@
2
2
title: Azure Operational Security | Microsoft Docs
3
3
description: Introduce yourself to Microsoft Azure Monitor logs, its services, and how it works by reading this overview.
4
4
services: security
5
-
author: UnifyCloud
6
-
manager: barbkess
7
-
editor: TomSh
8
-
5
+
author: msmbaldwin
9
6
ms.service: security
10
7
ms.subservice: security-fundamentals
11
8
ms.topic: article
12
-
ms.date: 11/21/2017
13
-
ms.author: TomSh
9
+
ms.date: 01/12/2026
10
+
ms.author: mbaldwin
14
11
15
12
---
16
13
17
-
# Azure Operational Security
14
+
# Azure operational security
18
15
## Introduction
19
16
20
17
### Overview
@@ -91,7 +88,7 @@ The Azure Monitor service manages your cloud-based data securely by using the fo
91
88
92
89
Protected data in Azure Backup is stored in a backup vault located in a particular geographic region. The data is replicated within the same region and, depending on the type of vault, may also be replicated to another region for further resiliency.
93
90
94
-
### Management Solutions
91
+
### Management solutions
95
92
[Azure Monitor](../../security-center/security-center-introduction.md) is Microsoft's cloud-based IT management solution that helps you manage and protect your on-premises and cloud infrastructure.
96
93
97
94
@@ -172,7 +169,7 @@ Cloud applications are complex with many moving parts. Monitoring provides data
172
169
173
170
In addition, you can use monitoring data to gain deep insights about your application. That knowledge can help you to improve application performance or maintainability, or automate actions that would otherwise require manual intervention.
174
171
175
-
### Azure Activity Log
172
+
### Azure activity log
176
173
177
174
178
175
It is a log that provides insight into the operations that were performed on resources in your subscription. The Activity Log was previously known as “Audit Logs” or “Operational Logs,” since it reports control-plane events for your subscriptions.
@@ -181,7 +178,7 @@ It is a log that provides insight into the operations that were performed on res
181
178
182
179
Using the Activity Log, you can determine the ‘what, who, and when’ for any write operations (PUT, POST, DELETE) taken on the resources in your subscription. You can also understand the status of the operation and other relevant properties. The Activity Log does not include read (GET) operations or operations for resources that use the Classic model.
183
180
184
-
### Azure Diagnostic Logs
181
+
### Azure diagnostic logs
185
182
186
183
These logs are emitted by a resource and provide rich, frequent data about the operation of that resource. The content of these logs varies by resource type.
187
184
@@ -325,7 +322,7 @@ This article explains
325
322
</ul>
326
323
</ul>
327
324
328
-
## Next Steps
325
+
## Next steps
329
326
330
327
-[Design and operational security](https://www.microsoft.com/trustcenter/security/designopsecurity)
Copy file name to clipboardExpand all lines: articles/security/fundamentals/shared-responsibility.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: msmbaldwin
6
6
ms.service: security
7
7
ms.subservice: security-fundamentals
8
8
ms.topic: article
9
-
ms.date: 01/08/2026
9
+
ms.date: 01/12/2026
10
10
ms.author: mbaldwin
11
11
#customer intent: As a cloud security administrator, I want to understand the shared responsibility model in Azure so that I can clearly identify which security tasks are mine and which are handled by Microsoft.
12
12
---
@@ -72,7 +72,7 @@ Microsoft is responsible for the underlying cloud infrastructure, which includes
72
72
-**Hypervisor** - Managing the virtualization layer that enables virtual machines in IaaS and PaaS.
73
73
-**Platform services** - In PaaS and SaaS, Microsoft manages operating systems, runtime environments, and middleware.
74
74
75
-
## AI Shared Responsibility
75
+
## AI shared responsibility
76
76
77
77
When using AI services, the shared responsibility model introduces unique considerations beyond traditional IaaS, PaaS, and SaaS. Microsoft is responsible for securing the AI infrastructure, model hosting, and platform-level safeguards. Customers, however, remain accountable for how AI is applied within their environment—this includes protecting sensitive data, managing prompt security, mitigating prompt injection risks, and ensuring compliance with organizational and regulatory requirements.
Copy file name to clipboardExpand all lines: articles/security/fundamentals/subdomain-takeover.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ author: msmbaldwin
8
8
ms.service: security
9
9
ms.subservice: security-fundamentals
10
10
ms.topic: article
11
-
ms.date: 04/16/2025
11
+
ms.date: 01/12/2026
12
12
ms.author: mbaldwin
13
13
14
14
---
@@ -182,7 +182,7 @@ It's often up to developers and operations teams to run cleanup processes to avo
182
182
- Investigate why the address wasn't rerouted when the resource was decommissioned.
183
183
- Delete the DNS record if it's no longer in use, or point it to the correct Azure resource (FQDN) owned by your organization.
184
184
185
-
### Clean up DNS pointers or Re-claim the DNS
185
+
### Clean up DNS pointers or re-claim the DNS
186
186
187
187
Upon deletion of the classic cloud service resource, the corresponding DNS is reserved as per Azure DNS policies. During the reservation period, re-use of the DNS will be forbidden EXCEPT for subscriptions belonging to the Microsoft Entra tenant of the subscription originally owning the DNS. After the reservation expires, the DNS is free to be claimed by any subscription. By taking DNS reservations, the customer is afforded some time to either 1) clean up any associations/pointers to said DNS or 2) re-claim the DNS in Azure. The recommendation would be to delete unwanted DNS entries at the earliest. The DNS name being reserved can be derived by appending the cloud service name to the DNS zone for that cloud.
0 commit comments