Documentation update

Author: ms-snarang

articles/healthcare-apis/known-issues.md

@@ -20,6 +20,7 @@ Refer to the table for details about resolution dates or possible workarounds.
 
 |Issue | Date discovered | Workaround | Date resolved |
 | :------------------------------------- | :------------ | :------------- | :------------- |
+| Customers are unable to select storage account in the FHIR service export configuration. The issue is caused by throttling due to a large number of resource groups and storage accounts, leading to errors like "Storage account does not exist" on the Export blade. | May 15, 2025 2:05 pm PST | PowerShell commands to configure the storage account for export manually:<br><br>Run the below command to install the Az Module: <br>```Install-Module -Name Az```<br><br> If Az module is already installed:<br>```Update-Module -Name Az```<br><br> Connect to Azure Account:<br>```Connect-AzAccount```<br><br>Initalize the variable resourceGroupName, fhirServiceName and storageAccountName:<br>```$resourceGroupName = "YOUR_RESOURCEGROUP_NAME"```<br>```$fhirServiceName = "YOUR_FHIRSERVICE_NAME"```<br>```$exportConfig = @{ "storageAccountName" = "YOUR_STORAGEACCOUNT_NAME" }```<br><br>Run the below command to set the storage account for export:<br>```Set-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName -ApiVersion "2021-11-01" -Properties @{ "exportConfiguration" = $exportConfig }```<br><br>Running the Below command will confirm if the setting was successful: <br>```Get-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName \| Select-Object -ExpandProperty Properties \| Select-Object -ExpandProperty exportConfiguration```| -- |
 | Patient-everything operation returns a 500 error when run using a SMART patient fhirUser token. |  April 9, 2025 | A fix is being released in the upcoming FHIR release. | |
 |Customers can't access FHIR, DICOM, or Medtech through the portal. | October 31, 2024 1:00 pm PST | ARM calls are still operational, and there's no disruption to existing services. | November 1, 2024  |
 |For FHIR instances created after August 19, 2024, diagnostic logs aren't available in log analytics workspace. |September 19, 2024 9:00 am PST| -- | October 17, 2024  |

articles/healthcare-apis/register-application-cli-rest.md

@@ -95,7 +95,8 @@ echo $clientsecret
 
 ## Change the flag for public client applications
 
-For public client applications, change the **Allow public client flows** flag to **Yes**. For confidential client applications, skip this step.
+For public client applications that use the OAuth authorization protocol or features as described in
+[Public client and confidential client applications](https://learn.microsoft.com/en-us/entra/identity-platform/msal-client-applications#when-should-you-enable-a-public-client-flow-in-your-app-registration), change the **Allow public client flows** flag to **Yes**. For confidential client applications, skip this step.
 
 [![Allow public client flows](media/app-registration-public-client.png)](media/app-registration-public-client.png#lightbox)
 

articles/healthcare-apis/register-application.md

@@ -39,7 +39,8 @@ If you keep this default value, the application registration is a **confidential
 
 [ ![Screenshot of confidential client application.](media/register-application-five.png) ](media/register-application-five.png#lightbox)
 
-If you change the default value to "Yes" for the "Allow public client flows" option in the advanced setting, the application registration is a **public client application** and a certificate or secret isn't required. The "Yes" value is useful when you want to use the client application in your mobile app or a JavaScript app where you don't want to store any secrets.
+If you change the default value to "Yes" for the "Allow public client flows" option in the advanced setting, the application registration is a **public client application** and a certificate or secret isn't required. The "Yes" value is useful when you want to build a public client application using the OAuth authorization protocol or features as described in
+[Public client and confidential client applications](https://learn.microsoft.com/en-us/entra/identity-platform/msal-client-applications#when-should-you-enable-a-public-client-flow-in-your-app-registration).
 
 For tools that require a redirect URL, select **Add a platform** to configure the platform.