Skip to content

Commit f88ff2c

Browse files
authored
Merge pull request #307285 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 35978da + 615cee5 commit f88ff2c

File tree

3 files changed

+6
-5
lines changed

3 files changed

+6
-5
lines changed

articles/azure-functions/security-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ As with any application or service, the goal is to run your function app with th
7878

7979
#### User management permissions
8080

81-
Functions supports built-in [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md). Azure roles supported by Functions are [Contributor](../role-based-access-control/built-in-roles.md#contributor), [Owner](../role-based-access-control/built-in-roles.md#owner), and [Reader](../role-based-access-control/built-in-roles.md#owner).
81+
Functions supports built-in [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md). Azure roles supported by Functions are [Contributor](../role-based-access-control/built-in-roles.md#contributor), [Owner](../role-based-access-control/built-in-roles.md#owner), and [Reader](../role-based-access-control/built-in-roles.md#reader).
8282

8383
Permissions are effective at the function app level. The Contributor role is required to perform most function app-level tasks. You also need the Contributor role along with the [Monitoring Reader permission](/azure/azure-monitor/roles-permissions-security#monitoring-reader) to be able to view log data in Application Insights. Only the Owner role can delete a function app.
8484

articles/sentinel/normalization-about-parsers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,12 +44,12 @@ The following table lists the available unifying parsers:
4444
| Schema | Unifying parser |
4545
| ------ | ------------------------- |
4646
| Audit Event | _Im_AuditEvent |
47-
| Authentication | imAuthentication |
47+
| Authentication | _Im_Authentication |
4848
| Dns | _Im_Dns |
49-
| File Event | imFileEvent |
49+
| File Event | _Im_FileEvent |
5050
| Network Session | _Im_NetworkSession |
51-
| Process Event | - imProcessCreate<br> - imProcessTerminate |
52-
| Registry Event | imRegistry |
51+
| Process Event | _Im_ProcessCreate<br> _Im_ProcessTerminate |
52+
| Registry Event | _Im_Registry |
5353
| Web Session | _Im_WebSession |
5454

5555

articles/storage/common/storage-network-security-perimeter.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,3 +56,4 @@ To associate a network security perimeter with a storage account, follow these [
5656

5757
- Learn more about [Azure network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md).
5858
- Dig deeper into [security recommendations for Azure Blob storage](../blobs/security-recommendations.md).
59+
- Enable [Diagnostic logs for Network Security Perimeter](/azure/private-link/network-security-perimeter-diagnostic-logs?source=recommendations).

0 commit comments

Comments
 (0)