Merge pull request #272616 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-arc/resource-bridge/troubleshoot-resource-bridge.md

@@ -263,9 +263,7 @@ When deploying the resource bridge on VMware vCenter, you might get an error say
 **Datastore** 
 
 - Allocate space
-
 - Browse datastore
-
 - Low level file operations
 
 **Folder** 
@@ -283,9 +281,7 @@ When deploying the resource bridge on VMware vCenter, you might get an error say
 **Resource**
 
 - Assign virtual machine to resource pool
-
 - Migrate powered off virtual machine
-
 - Migrate powered on virtual machine
 
 **Sessions**
@@ -295,125 +291,68 @@ When deploying the resource bridge on VMware vCenter, you might get an error say
 **vApp**
 
 - Assign resource pool
-
 - Import 
 
 **Virtual machine**
 
 - Change Configuration
-
   - Acquire disk lease
-
   - Add existing disk
-
   - Add new disk
-
   - Add or remove device
-
   - Advanced configuration
-
   - Change CPU count
-
   - Change Memory
-
   - Change Settings
-
   - Change resource
-
   - Configure managedBy
-
   - Display connection settings
-
   - Extend virtual disk
-
   - Modify device settings
-
   - Query Fault Tolerance compatibility
-
   - Query unowned files
-
   - Reload from path
-
   - Remove disk
-
   - Rename
-
   - Reset guest information
-
   - Set annotation
-
   - Toggle disk change tracking
-
   - Toggle fork parent
-
   - Upgrade virtual machine compatibility
-
 - Edit Inventory
-
   - Create from existing
-
   - Create new
-
   - Register
-
   - Remove
-
   - Unregister
-
 - Guest operations
-
   - Guest operation alias modification
-
   - Guest operation modifications
-
   - Guest operation program execution
-
   - Guest operation queries
-
 - Interaction
-
   - Connect devices
-
   - Console interaction
-
   - Guest operating system management by VIX API
-
   - Install VMware Tools
-
   - Power off
-
   - Power on
-
   - Reset
-
   - Suspend
-
 - Provisioning
-
   - Allow disk access
-
   - Allow file access
-
   - Allow read-only disk access
-
   - Allow virtual machine download
-
   - Allow virtual machine files upload
-
   - Clone virtual machine
-
   - Deploy template
-  
   - Mark as template
-
   - Mark as virtual machine
-
+  - Customize guest
 - Snapshot management
-
   - Create snapshot
-
   - Remove snapshot
-
   - Revert to snapshot
 
 ## Next steps

articles/container-registry/container-registry-import-images.md

@@ -364,6 +364,15 @@ az acr import \
 Import-AzContainerRegistryImage -RegistryName myregistry -ResourceGroupName myResourceGroup -SourceRegistryUri docker.io/sourcerepo -SourceImage sourcerrepo:tag -Username <username> -Password <password>
 ```
 
+### Troubleshoot Import Container Images
+#### Symptoms and Causes
+- `The remote server may not be RFC 7233 compliant`
+  - The [distribution-spec](https://github.com/opencontainers/distribution-spec/blob/main/spec.md) allows range header form of `Range: bytes=<start>-<end>`. However, the remote server may not be RFC 7233 compliant.
+- `Unexpected response status code`
+  - Get an unexpected response status code from source repository when doing range query.
+- `Unexpected length of body in response`
+  - The received content length does not match the size expected. Expected size is decided by blob size and range header.
+
 ---
 
 ## Next steps

articles/search/query-simple-syntax.md

@@ -48,8 +48,8 @@ Strings passed to the `search` parameter can include terms or phrases in any sup
 
 + A *phrase search* is an exact phrase enclosed in quotation marks `" "`. For example, while ```Roach Motel``` (without quotes) would search for documents containing ```Roach``` and/or ```Motel``` anywhere in any order, ```"Roach Motel"``` (with quotes) will only match documents that contain that whole phrase together and in that order (lexical analysis still applies). 
 
-  Depending on your search client, you might need to escape the quotation marks in a phrase search. For example, in a POST request, a phrase search on `"Roach Motel"` in the request body might be specified as `"\"Roach Motel\""`.
-
+Depending on your search client, you might need to escape the quotation marks in a phrase search. For example, in a POST request, a phrase search on `"Roach Motel"` in the request body might be specified as `"\"Roach Motel\""`. If you're using the Azure SDKs, the search client escapes the quotation marks when it serializes the search text. Your search phrase can be sent be as "Roach Motel".
+  
 By default, all strings passed in the `search` parameter undergo lexical analysis. Make sure you understand the tokenization behavior of the analyzer you're using. Often, when query results are unexpected, the reason can be traced to how terms are tokenized at query time. You can [test tokenization on specific strings](/rest/api/searchservice/test-analyzer) to confirm the output.
 
 Any text input with one or more terms is considered a valid starting point for query execution. Azure AI Search will match documents containing any or all of the terms, including any variations found during analysis of the text.