Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into issuessolving

Author: liudan66

articles/healthcare-apis/fhir/fhir-faq.md

@@ -33,7 +33,7 @@ In the managed service, you can't access the underlying data. This is to ensure
 
 ### What identity provider do you support?
 
-We support Microsoft Entra ID as the identity provider.
+We support Microsoft Entra ID and third party identity provider that support OpenID connect.
 
 ### Can I use Azure AD B2C with the FHIR service?
 
@@ -47,11 +47,16 @@ For more information, see [Supported FHIR features](fhir-features-supported.md).
 
 ### What is the difference between Azure API for FHIR and the FHIR service in the Azure Health Data Services?
 
-Azure API for FHIR was our initial generally available product and is being retired as of September 30, 2026. The Azure Health Data Services FHIR service supports additional capabilities such as: 
+Azure API for FHIR was our initial generally available product and is being retired as of September 30, 2026. Below table provides difference between Azure API for FHIR and Azure Health Data Services, FHIR service
 
-- [Transaction bundles](https://www.hl7.org/fhir/http.html#transaction).
-- [Incremental Import](configure-import-data.md)
-- [Autoscaling](fhir-service-autoscale.md) enabled by default
+|Capabilities|Azure API for FHIR|Azure Health Data Services|
+|------------|------------------|--------------------------|
+|**Data ingress**|Tools available in OSS|$import operation. For information visit [Import operation](configure-import-data.md)|
+|**Autoscaling**|Supported on request and incurs charge|[Autoscaling](fhir-service-autoscale.md) enabled by default at no extra charge|
+|**Search parameters**|Bundle type supported: Batch <br> • Include and revinclude, iterate modifier not supported  <br> • Sorting supported by first name, last name, birthdate and clinical date|Bundle type supported: Batch and transaction  <br> • [Selectable search parameters](selectable-search-parameters.md)  <br> • Include, revinclude, and iterate modifier is supported <br>• Sorting supported by string and dateTime fields|
+|**Events**|Not Supported|Supported|
+|**Convert-data**|Supports enabling "Allow trusted services" in Account container registry| There is a known issue -"Enabling "Allow trusted services" in the Account Container Registry may result in access issues when attempting to use the container registry from the FHIR service."|
+|**Business continuity**|Supported:<br> • Cross region DR (disaster recovery)  <br>|Supported: <br> • PITR (point in time recovery) <br> • Availability zone support|
 
 By default each Azure Health Data Services, FHIR instance is limited to storage capacity of 4TB.
 To provision a FHIR instance with storage capacity beyond 4TB, create support request with Issue type 'Service and Subscription limit (quotas)'.
@@ -121,21 +126,10 @@ We currently support posting [batch bundles](https://www.hl7.org/fhir/valueset-b
 
 We support the [$patient-everything operation](patient-everything.md) which will get you all data related to a single patient. 
 
-### What is the default sort when searching for resources in the FHIR service?
-
-We support sorting by string and dateTime fields in the FHIR service. For more information about other supported search parameters, see [Overview of FHIR search](overview-of-search.md).
-
 ### Does the FHIR service support any terminology operations?
 
 No, the FHIR service doesn't support terminology operations today.
 
-### What are the differences between delete types in the FHIR service? 
-
-There are two basic Delete types supported within the FHIR service. They are [Delete and Conditional Delete](rest-api-capabilities.md#delete-and-conditional-delete).
-
-* With Delete, you can choose to do a soft delete (most common type) and still be able to recover historic versions of your record.
-* With Conditional Delete, you can pass search criteria to delete a resource one item at a time or several at a time.
-* If you passed the `hardDelete` parameter with either Delete or Conditional Delete, all the records and history are deleted and unrecoverable.
 
 ## Using the FHIR service
 

articles/postgresql/migrate/migration-service/concepts-migration-service-runtime-server.md

@@ -28,16 +28,25 @@ The migration runtime server is essential for transferring data between differen
 
 ## How do you use the Migration Runtime Server feature?
 
-To use the Migration Runtime Server feature within the migration service in Azure Database for PostgreSQL, follow these steps in the Azure portal:
+To use the Migration Runtime Server feature within the migration service in Azure Database for PostgreSQL, you can select the appropriate migration option either through the Azure portal during the setup or by specifying the `migrationRuntimeResourceId` in the JSON properties file during the migration create command in the Azure CLI. Here's how to do it in both methods:
+
+### Use the Azure portal
 
 - Sign in to the Azure portal and access the migration service (from the target server) in the Azure Database for PostgreSQL instance.
 - Begin a new migration workflow within the service.
 - When you reach the "Select runtime server" tab, use the Migration Runtime Server by selecting "Yes."
-Choose your Azure subscription and resource group and the location of the VNet-integrated Azure Database for PostgreSQL—Flexible server.
+- Choose your Azure subscription and resource group and the location of the VNet-integrated Azure Database for PostgreSQL—Flexible server.
 - Select the appropriate Azure Database for PostgreSQL Flexible Server to serve as your Migration Runtime Server.
 
 :::image type="content" source="media/concepts-migration-service-runtime-server/select-runtime-server.png" alt-text="Screenshot of selecting migration runtime server.":::
 
+### Use Azure CLI
+
+- Open your command-line interface.
+- Ensure you have the Azure CLI installed and you're logged into your Azure account using az sign-in.
+- The version should be at least 2.62.0 or above to use the migration runtime server option.
+- The `az postgres flexible-server migration create` command requires a JSON file path as part of `--properties` parameter, which contains configuration details for the migration. Provide the `migrationRuntimeResourceId` in the JSON properties file.
+
 ## Migration Runtime Server essentials
 
 - **Minimal Configuration**—Despite being created from an Azure Database for PostgreSQL Flexible Server, the migration runtime server solely facilitates migration without the need for HA, backups, version specificity, or advanced storage features.

articles/postgresql/migrate/migration-service/how-to-setup-azure-cli-commands-postgresql.md

@@ -141,6 +141,7 @@ The `az postgres flexible-server migration create` command requires a JSON file
 | `targetServerUserName` | The default value is the admin user created during the creation of the PostgreSQL target flexible server, and the password provided is used for authentication against this user. |
 | `dbsToMigrate` | Specify the list of databases that you want to migrate to Flexible Server. You can include a maximum of eight database names at a time. Providing the list of DBs in array format. |
 | `overwriteDBsInTarget` | When set to true (default), if the target server happens to have an existing database with the same name as the one you're trying to migrate, the migration service automatically overwrites the database |
+| `migrationRuntimeResourceId` | Required if a runtime server needs to be used for migration. The format is - `/subscriptions/<<Subscription ID>>/resourceGroups/<<Resource Group Name>>/providers/Microsoft.DBforPostgreSQL/flexibleServers/<<PostgreSQL Flexible Server name>>` |
 | `sourceType` | Required parameter. Values can be - on-premises, AWS_RDS, AzureVM, PostgreSQLSingleServer |
 | `sslMode` | SSL modes for migration. SSL mode for PostgreSQLSingleServer is VerifyFull and Prefer/Require for other source types. |