Skip to content

Commit c0bc9a2

Browse files
v-andreacov-andreaco
authored
Merge pull request #171467 from MicrosoftDocs/master
Sunday 4pm publish to live
2 parents e6a0573 + c5427ce commit c0bc9a2

14 files changed

+59
-59
lines changed

‎articles/azure-monitor/agents/data-sources-windows-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ As you type the name of an event log, Azure Monitor provides suggestions of comm
2626
[![Configure Windows events](media/data-sources-windows-events/configure.png)](media/data-sources-windows-events/configure.png#lightbox)
2727

2828
> [!IMPORTANT]
29-
> You can't configure collection of security events from the workspace. You must used [Azure Security Center](../../security-center/security-center-enable-data-collection.md) or [Azure Sentinel](../../sentinel/connect-windows-security-events.md) to collect security events.
29+
> You can't configure collection of security events from the workspace. You must use [Azure Security Center](../../security-center/security-center-enable-data-collection.md) or [Azure Sentinel](../../sentinel/connect-windows-security-events.md) to collect security events.
3030
3131

3232
> [!NOTE]

‎articles/azure-monitor/visualize/vmext-troubleshoot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ If the *Microsoft Monitoring Agent* VM extension is not installing or reporting,
3737
3. Ensure the virtual machine can run PowerShell scripts
3838
4. Ensure permissions on C:\Windows\temp haven’t been changed
3939
5. View the status of the Microsoft Monitoring Agent by typing the following in an elevated PowerShell window on the virtual machine `(New-Object -ComObject 'AgentConfigManager.MgmtSvcCfg').GetCloudWorkspaces() | Format-List`
40-
6. Review the Microsoft Monitoring Agent setup log files in `C:\Windows\System32\config\systemprofile\AppData\Local\SCOM\Logs`
40+
6. Review the Microsoft Monitoring Agent setup log files in `C:\WindowsAzure\Logs\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.18053.0\`. Note that this path will change based on the version number of the agent.
4141

4242
For more information, see [troubleshooting Windows extensions](../../virtual-machines/extensions/oms-windows.md).
4343

@@ -55,4 +55,4 @@ For more information, see [troubleshooting Linux extensions](../../virtual-machi
5555

5656
## Next steps
5757

58-
For additional troubleshooting guidance related to the Log Analytics agent for Linux hosted on computers outside of Azure, see [Troubleshoot Azure Log Analytics Linux Agent](../agents/agent-linux-troubleshoot.md).
58+
For additional troubleshooting guidance related to the Log Analytics agent for Linux hosted on computers outside of Azure, see [Troubleshoot Azure Log Analytics Linux Agent](../agents/agent-linux-troubleshoot.md).

‎articles/security-center/recommendations-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article lists Azure Security Center's security recommendations
44
author: memildin
55
ms.service: security-center
66
ms.topic: reference
7-
ms.date: 07/25/2021
7+
ms.date: 09/05/2021
88
ms.author: memildin
99
ms.custom: generated
1010
---

‎articles/security-center/security-center-just-in-time.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: rkarlin
77

88
ms.service: security-center
99
ms.topic: how-to
10-
ms.date: 07/12/2020
10+
ms.date: 09/05/2021
1111
ms.author: memildin
1212

1313
---
@@ -64,7 +64,7 @@ From Security Center, you can enable and configure the JIT VM access.
6464
- the last user
6565
- **Not configured** - VMs without JIT enabled, but that can support JIT. We recommend that you enable JIT for these VMs.
6666
- **Unsupported** - VMs without JIT enabled and which don't support the feature. Your VM might be in this tab for the following reasons:
67-
- Missing network security group (NSG) - JIT requires an NSG to be configured
67+
- Missing network security group (NSG) or Azure Firewall - JIT requires an NSG to be configured or a Firewall configuration (or both)
6868
- Classic VM - JIT supports VMs that are deployed through Azure Resource Manager, not 'classic deployment'. [Learn more about classic vs Azure Resource Manager deployment models](../azure-resource-manager/management/deployment-models.md).
6969
- Other - Your VM might be in this tab if the JIT solution is disabled in the security policy of the subscription or the resource group.
7070

‎includes/asc-recs-appservices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: memildin
33
ms.service: security-center
44
ms.topic: include
5-
ms.date: 07/25/2021
5+
ms.date: 09/05/2021
66
ms.author: memildin
77
ms.custom: generated
88
---

‎includes/asc-recs-compute.md

Lines changed: 6 additions & 6 deletions
Large diffs are not rendered by default.

‎includes/asc-recs-container.md

Lines changed: 4 additions & 4 deletions
Large diffs are not rendered by default.

‎includes/asc-recs-data.md

Lines changed: 9 additions & 9 deletions
Large diffs are not rendered by default.

‎includes/asc-recs-identityandaccess.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: memildin
33
ms.service: security-center
44
ms.topic: include
5-
ms.date: 07/25/2021
5+
ms.date: 09/05/2021
66
ms.author: memildin
77
ms.custom: generated
88
---

‎includes/asc-recs-iot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: memildin
33
ms.service: security-center
44
ms.topic: include
5-
ms.date: 07/25/2021
5+
ms.date: 09/05/2021
66
ms.author: memildin
77
ms.custom: generated
88
---

0 commit comments

Comments
 (0)