Merge pull request #235142 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: huypub

articles/active-directory/external-identities/reset-redemption-status.md

@@ -82,7 +82,7 @@ Connect-MgGraph -Scopes "User.ReadWrite.All"
 $user = Get-MgUser -Filter "startsWith(mail, '[email protected]')"
 New-MgInvitation `
     -InvitedUserEmailAddress $user.Mail `
-    -InviteRedirectUrl "http://myapps.microsoft.com" `
+    -InviteRedirectUrl "https://myapps.microsoft.com" `
     -ResetRedemption `
     -SendInvitationMessage `
     -InvitedUser $user

articles/cognitive-services/openai/quotas-limits.md

@@ -22,7 +22,7 @@ The following sections provide you with a quick guide to the quotas and limits t
 
 | Limit Name | Limit Value |
 |--|--|
-| OpenAI resources per region | 2 | 
+| OpenAI resources per region within Azure subscription | 2 | 
 | Requests per minute per model* | Davinci-models (002 and later): 120  <br> ChatGPT model (preview): 300 <br> GPT-4 models (preview): 18 <br> All other models: 300 |
 | Tokens per minute per model* | Davinci-models (002 and later): 40,000  <br> ChatGPT model: 120,000 <br> All other models: 120,000 |
 | Max fine-tuned model deployments* | 2 |

articles/event-grid/handler-functions.md

@@ -47,7 +47,7 @@ We recommend that you use the first approach (Event Grid trigger) as it has the
 			{
 				"resourceId": "/subscriptions/<AZURE SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP NAME>/providers/Microsoft.Web/sites/<FUNCTION APP NAME>/functions/<FUNCTION NAME>",
 				"maxEventsPerBatch": 10,
-				"preferredBatchSizeInKilobytes": 6400
+				"preferredBatchSizeInKilobytes": 64
 			}
 		},
 		"eventDeliverySchema": "EventGridSchema"

articles/network-watcher/traffic-analytics-schema.md

@@ -107,7 +107,6 @@ The following table lists the fields in the schema and what they signify.
 | SrcIP_s |	Source IP address |	Will be blank in case of AzurePublic and ExternalPublic flows. |
 | DestIP_s | Destination IP address	| Will be blank in case of AzurePublic and ExternalPublic flows. |
 | VMIP_s | IP of the VM	| Used for AzurePublic and ExternalPublic flows. |
-| PublicIP_s | Public IP addresses | Used for AzurePublic and ExternalPublic flows. |
 | DestPort_d | Destination Port | Port at which traffic is incoming. |
 | L4Protocol_s	| *	T <br> * U 	| Transport Protocol. T = TCP <br> U = UDP. |
 | L7Protocol_s	| Protocol Name	| Derived from destination port. |

articles/resource-mover/overview.md

@@ -57,7 +57,7 @@ You can move resources across regions in the Resource Mover hub or from within a
 
 Using Resource Mover, you can currently move the following resources across regions:
 
-- Azure VMs and associated disks
+- Azure VMs and associated disks (Azure Spot VMs are not currently supported)
 - Encrypted Azure VMs and associated disks. This includes VMs with Azure disk encryption enabled and Azure VMs using default server-side encryption (both with platform-managed keys and customer-managed keys)
 - NICs
 - Availability sets 

articles/synapse-analytics/sql-data-warehouse/maintenance-scheduling.md

@@ -32,10 +32,8 @@ All maintenance operations should finish within the specified maintenance window
 
 Integration with Service Health notifications and the Resource Health Check Monitor allows customers to stay informed of impending maintenance activity. This automation takes advantage of Azure Monitor. You can decide how you want to be notified of impending maintenance events. Also, you can choose which automated flows will help you manage downtime and minimize operational impact.
 
-A 24-hour advance notification precedes all maintenance events that aren't for the DW400c and lower tiers.
-
 > [!NOTE]
-> In the event we are required to deploy a time critical update, advanced notification times may be significantly reduced. This could occur outside an identified maintenance window due to the critical nature of the update.
+> A 24-hour advance notification precedes all maintenance events. In the event we are required to deploy a time critical update, advanced notification times may be significantly reduced. This could occur outside an identified maintenance window due to the critical nature of the update.
 
 If you received advance notification that maintenance will take place, but maintenance can't be performed during the time period in the notification, you'll receive a cancellation notification. Maintenance will then resume during the next scheduled maintenance period.