document changes

Author: ms-snarang

articles/healthcare-apis/known-issues.md

@@ -20,7 +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```| -- |
+| Customers are unable to select storage account in the FHIR instance 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 doesn't 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 this 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>Initialize 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 this 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 this command confirms  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  |