Merge pull request #267007 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)

Author: Taojunshen

articles/azure-cache-for-redis/cache-tls-configuration.md

@@ -16,7 +16,7 @@ ms.author: franlanglois
 Transport Layer Security (TLS) is a cryptographic protocol that provides secure communication over a network. Azure Cache for Redis supports TLS on all tiers. When create a service that uses an Azure Cache for Redis instance, we strongly encourage you to connect using TLS.
 
 > [!IMPORTANT]
-> Starting October 1, 2024, TLS 1.0 and 1.1 will no longer be supported. You should use TLS 1.2 or 1.3 instead.
+> Starting November 01, 2024, TLS 1.0 and 1.1 will no longer be supported. You should use TLS 1.2 or 1.3 instead.
 >
 
 ## Scope of availability

articles/azure-monitor/logs/resource-manager-cluster.md

@@ -34,6 +34,10 @@ param location string = resourceGroup().location
 
 @description('Specify the capacity reservation value.')
 @allowed([
+  100
+  200
+  300
+  400
   500
   1000
   2000
@@ -87,6 +91,10 @@ resource cluster 'Microsoft.OperationalInsights/clusters@2021-06-01' = {
     "CommitmentTier": {
       "type": "int",
       "allowedValues": [
+        100,
+        200,
+        300,
+        400,
         500,
         1000,
         2000,

articles/sentinel/entities-reference.md

@@ -27,7 +27,7 @@ Learn more about [strong and weak identifiers](entities.md#strong-and-weak-ident
 | [**Host**](#host) | DnsDomain<br>NTDomain<br>HostName<br>*FullName \**<br>NetBiosName<br>AzureID<br>OMSAgentID<br>OSFamily<br>OSVersion<br>IsDomainJoined | HostName+NTDomain<br>HostName+DnsDomain<br>NetBiosName+NTDomain<br>NetBiosName+DnsDomain<br>AzureID<br>OMSAgentID | HostName<br>NetBiosName |
 | [**IP**](#ip) | Address<br>AddressScope | Address [\*\*](#strong-identifiers-of-an-ip-entity)<br>Address+AddressScope [\*\*](#strong-identifiers-of-an-ip-entity) | |
 | [**URL**](#url) | Url | Url *(if absolute URL)* [\*\*](#strong-identifiers-of-a-url-entity) | Url *(if relative URL)* [\*\*](#strong-identifiers-of-a-url-entity) |
-| [**Azure resource**](#azure-resource) | ResourceId | ResourceId | |
+| [**AzureResource**](#azure-resource) | ResourceId | ResourceId | |
 | [**Cloud application**](#cloud-application)<br>*(CloudApplication)* | AppId<br>Name<br>InstanceName | AppId<br>Name<br>AppId+InstanceName<br>Name+InstanceName | |
 | [**DNS Resolution**](#dns-resolution) | DomainName | DomainName+*DnsServerIp*+*HostIpAddress* | DomainName+*HostIpAddress* |
 | [**File**](#file) | Directory<br>Name | Directory+Name | |
@@ -65,7 +65,7 @@ The following section contains a more in-depth look at the full schemas of each
 - [Process](#process)
 - [Cloud application](#cloud-application)
 - [DNS resolution](#dns-resolution)
-- [Azure resource](#azure-resource)
+- [AzureResource](#azure-resource)
 - [File hash](#file-hash)
 - [Registry key](#registry-key)
 - [Registry value](#registry-value)
@@ -80,6 +80,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### Account
 
+*Entity name: Account*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'account' |
@@ -137,6 +139,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### Host
 
+*Entity name: Host*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'host' |
@@ -190,6 +194,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### Malware
 
+*Entity name: Malware*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'malware' |
@@ -206,6 +212,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### File
 
+*Entity name: File*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'file' |
@@ -229,6 +237,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### Process
 
+*Entity name: Process*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'process' |
@@ -306,6 +316,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### Azure resource
 
+*Entity name: AzureResource*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'azure-resource' |
@@ -397,6 +409,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### URL
 
+*Entity name: Url*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | Type | String | 'url' |
@@ -459,6 +473,8 @@ The following section contains a more in-depth look at the full schemas of each
 
 ### Mailbox
 
+*Entity name: Mailbox*
+
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | **Type** | String | 'mailbox' |

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

@@ -22,7 +22,7 @@ Storage accounts have a public endpoint that's accessible through the internet.
 
 The Azure Storage firewall provides access control for the public endpoint of your storage account. You can also use the firewall to block all access through the public endpoint when you're using private endpoints. Your firewall configuration also enables trusted Azure platform services to access the storage account.
 
-An application that accesses a storage account when network rules are in effect still requires proper authorization for the request. Authorization is supported with Microsoft Entra credentials for blobs and queues, with a valid account access key, or with a shared access signature (SAS) token. When you configure a blob container for anonymous access, requests to read data in that container don't need to be authorized. The firewall rules remain in effect and will block anonymous traffic.
+An application that accesses a storage account when network rules are in effect still requires proper authorization for the request. Authorization is supported with Microsoft Entra credentials for blobs, tables, file shares and queues, with a valid account access key, or with a shared access signature (SAS) token. When you configure a blob container for anonymous access, requests to read data in that container don't need to be authorized. The firewall rules remain in effect and will block anonymous traffic.
 
 Turning on firewall rules for your storage account blocks incoming requests for data by default, unless the requests originate from a service that operates within an Azure virtual network or from allowed public IP addresses. Requests that are blocked include those from other Azure services, from the Azure portal, and from logging and metrics services.