From dadecab48a4152be4c518a0c082fe94a4093948e Mon Sep 17 00:00:00 2001 From: Shashank Narang Date: Fri, 11 Oct 2024 13:27:32 +0530 Subject: [PATCH 1/2] Document Update --- docs/DefaultDeployment.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/DefaultDeployment.md b/docs/DefaultDeployment.md index 2125bb5eca..74a5fe64d2 100644 --- a/docs/DefaultDeployment.md +++ b/docs/DefaultDeployment.md @@ -57,6 +57,9 @@ We recommend starting with the SQL deployment as it offers the most features. Ho Note that when you deploy from our templates, it is set to deploy with $export enabled. As part of the export setup, a storage account is automatically created along with roles. The creation of this storage account and roles requires that you have contributor access at the subscription level. If the person deploying does not have contributor access at the subscription level, the deployment will fail. To deploy successfully in this scenario, you can deploy with export set to false. If you need to use export, it can be configured to true after deployment by someone with contributor access at the subscription level. It takes a few more steps as someone will need to create and link the storage account (it won’t automatically get created) but from there it will work exactly as if you had set it to true at provisioning. To deploy the backend SQL Server, Azure Web App, and FHIR server code, use the buttons below to deploy through the Azure Portal. If you would like to protect the FHIR API with token authorization, you will need to supply application registration details as described above. +###### NOTE +>If you select a SQL database deployment with the Schema Update set to TOOL, you must run the SQL migration tool immediately after the deployment completes successfully.
+The detailed information about this tool is provided [here](SchemaMigrationTool.md). The FHIR server can be deployed using all free Azure resources. When deploying select 'F1' as the App Service Plan Sku, 'Yes' to use the Cosmos DB Free Tier, and FhirServerCosmosDB as the Solution Type. The free app service plan and Cosmos Db account have restrictions that can be seen on their respective doc pages: [App Service plan overview](https://docs.microsoft.com/en-us/azure/app-service/overview-hosting-plans), [Cosmos DB free tier](https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-dev-test#azure-cosmos-db-free-tier) From 29b7821f55551614a0c10ce0b0b3b36815da8d3c Mon Sep 17 00:00:00 2001 From: Shashank Narang Date: Mon, 14 Oct 2024 11:19:54 +0530 Subject: [PATCH 2/2] Update the doc --- docs/DefaultDeployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DefaultDeployment.md b/docs/DefaultDeployment.md index 74a5fe64d2..9dd8fac9fd 100644 --- a/docs/DefaultDeployment.md +++ b/docs/DefaultDeployment.md @@ -59,7 +59,7 @@ Note that when you deploy from our templates, it is set to deploy with $export e To deploy the backend SQL Server, Azure Web App, and FHIR server code, use the buttons below to deploy through the Azure Portal. If you would like to protect the FHIR API with token authorization, you will need to supply application registration details as described above. ###### NOTE >If you select a SQL database deployment with the Schema Update set to TOOL, you must run the SQL migration tool immediately after the deployment completes successfully.
-The detailed information about this tool is provided [here](SchemaMigrationTool.md). +Detailed information about this tool is provided [here](SchemaMigrationTool.md). The FHIR server can be deployed using all free Azure resources. When deploying select 'F1' as the App Service Plan Sku, 'Yes' to use the Cosmos DB Free Tier, and FhirServerCosmosDB as the Solution Type. The free app service plan and Cosmos Db account have restrictions that can be seen on their respective doc pages: [App Service plan overview](https://docs.microsoft.com/en-us/azure/app-service/overview-hosting-plans), [Cosmos DB free tier](https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-dev-test#azure-cosmos-db-free-tier)