Skip to content

Commit

Permalink
Document Update (#4671)
Browse files Browse the repository at this point in the history
* Document Update

* Update the doc

---------

Co-authored-by: Shashank Narang <v-shnarang@microsoft.com>
  • Loading branch information
v-shnarang and Shashank Narang authored Nov 19, 2024
1 parent 0adbfa9 commit c4a33cc
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions docs/DefaultDeployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.<br>
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)

Expand Down

0 comments on commit c4a33cc

Please sign in to comment.