Skip to content

Commit e88196b

Browse files
authored
Merge pull request #202849 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents a2af4fc + 4b61b54 commit e88196b

File tree

8 files changed

+73
-69
lines changed

8 files changed

+73
-69
lines changed

articles/active-directory-b2c/enable-authentication-web-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ npm install passport-azure-ad
126126
npm install morgan
127127
```
128128

129-
The [morgen package](https://www.npmjs.com/package/morgan) is an HTTP request logger middleware for Node.js.
129+
The [morgan package](https://www.npmjs.com/package/morgan) is an HTTP request logger middleware for Node.js.
130130

131131
---
132132

articles/active-directory/app-proxy/application-proxy-configure-single-sign-on-with-headers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ When you've completed all these steps, your app should be running and available.
8686
## Considerations
8787

8888
- Application Proxy is used to provide remote access to apps on-premises or on private cloud. Application Proxy is not recommended to handle traffic originating internally from the corporate network.
89-
- Access to header-based authentication applications should be restricted to only traffic from the connector or other permitted header-based authentication solution. This is commonly done through restricting network access to the application using a firewall or IP restriction on the application server.
89+
- **Access to header-based authentication applications should be restricted to only traffic from the connector or other permitted header-based authentication solution**. This is commonly done through restricting network access to the application using a firewall or IP restriction on the application server to avoid exposing to the attackers.
9090

9191
## Next steps
9292

articles/defender-for-cloud/alerts-reference.md

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

articles/defender-for-iot/organizations/alert-engine-messages.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ Malware engine alerts describe detected malicious network activity.
201201
| Malware Test File Detected - EICAR AV Success | An EICAR AV test file was detected in traffic between two devices (over any transport - TCP or UDP). The file isn't malware. It's used to confirm that the antivirus software is installed correctly. Demonstrate what happens when a virus is found, and check internal procedures and reactions when a virus is found. Antivirus software should detect EICAR as if it were a real virus. | Major |
202202
| Suspicion of Conficker Malware | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Major |
203203
| Suspicion of Denial Of Service Attack | A source device attempted to initiate an excessive number of new connections to a destination device. This may indicate a Denial Of Service (DOS) attack against the destination device, and might interrupt device functionality, affect performance and service availability, or cause unrecoverable errors. | Critical |
204-
| Suspicion of Malicious Activity | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Major |
204+
| Suspicion of Malicious Activity | Suspicious network activity was detected. This activity may be associated with an attack that triggered known 'Indicators of Compromise' (IOCs). Alert metadata should be reviewed by the security team. | Major |
205205
| Suspicion of Malicious Activity (BlackEnergy) | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Critical |
206206
| Suspicion of Malicious Activity (DarkComet) | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Critical |
207207
| Suspicion of Malicious Activity (Duqu) | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Critical |
@@ -219,7 +219,7 @@ Malware engine alerts describe detected malicious network activity.
219219
| Suspicion of Remote Code Execution with PsExec | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Major |
220220
| Suspicion of Remote Windows Service Management | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Major |
221221
| Suspicious Executable File Detected on Endpoint | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Major |
222-
| Suspicious Traffic Detected | Suspicious network activity was detected. This activity may be associated with an attack exploiting a method used by known malware. | Critical |
222+
| Suspicious Traffic Detected | Suspicious network activity was detected. This activity may be associated with an attack that triggered known 'Indicators of Compromise' (IOCs). Alert metadata should be reviewed by the security team | Critical |
223223
| Backup Activity with Antivirus Signatures | Traffic detected between the source device and the destination backup server triggered this alert. The traffic includes backup of antivirus software that might contain malware signatures. This is most likely legitimate backup activity. | Warning |
224224

225225
## Operational engine alerts
@@ -271,4 +271,4 @@ Operational engine alerts describe detected operational incidents, or malfunctio
271271
## Next steps
272272

273273
You can [Manage alert events](how-to-manage-the-alert-event.md).
274-
Learn how to [Forward alert information](how-to-forward-alert-information-to-partners.md).
274+
Learn how to [Forward alert information](how-to-forward-alert-information-to-partners.md).

articles/managed-grafana/overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,3 +36,4 @@ You can create dashboards instantaneously by importing existing charts directly
3636

3737
> [!div class="nextstepaction"]
3838
> [Create an Azure Managed Grafana Preview instance using the Azure portal](./quickstart-managed-grafana-portal.md)
39+

articles/managed-grafana/quickstart-managed-grafana-cli.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ Get started by creating an Azure Managed Grafana Preview workspace using the Azu
1616
> [!NOTE]
1717
> The CLI experience for Azure Managed Grafana Preview is part of the amg extension for the Azure CLI (version 2.30.0 or higher). The extension will automatically install the first time you run an `az grafana` command.
1818

19+
> [!NOTE]
20+
> Azure Managed Grafana doesn't support personal [Microsoft accounts](https://account.microsoft.com) currently.
21+
1922
## Prerequisite
2023

2124
An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/dotnet).

articles/managed-grafana/quickstart-managed-grafana-portal.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ Get started by creating an Azure Managed Grafana Preview workspace using the Azu
1717

1818
An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/dotnet).
1919

20+
> [!NOTE]
21+
> Azure Managed Grafana doesn't support personal [Microsoft accounts](https://account.microsoft.com) currently.
22+
2023
## Create a Managed Grafana workspace
2124

2225
1. Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.

articles/storage/blobs/storage-blobs-static-site-github-actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: devx-track-javascript, github-actions-azure, devx-track-azurecli
1212

1313
---
1414

15-
# Set up a GitHub Actions workflow to deploy your static website in Azure Storage
15+
# Use GitHub Actions workflow to deploy your static website in Azure Storage
1616

1717
Get started with [GitHub Actions](https://docs.github.com/en/actions) by using a workflow to deploy a static site to an Azure storage account. Once you have set up a GitHub Actions workflow, you will be able to automatically deploy your site to Azure from GitHub when you make changes to your site's code.
1818

0 commit comments

Comments
 (0)