Merge pull request #97070 from CaitlinV39/master

Updated the application areas

Author: Jak-MS

articles/healthcare-apis/TOC.yml

@@ -28,17 +28,25 @@
     href: tutorial-2-setup-environment.md
   - name: 2. Set up application configuration
     href: tutorial-1-decision-flow.md
-  - name: 3. Register a confidential client app
-    href: register-confidential-azure-ad-client-app.md
-  - name: 4. Configure additional settings
+  - name: 3. Configure additional settings
     href: azure-api-for-fhir-additional-settings.md
-  - name: 5. Write an application
+  - name: 4. Write an application
     href: tutorial-3-connect-to-endpoint.md
   - name: Access FHIR API with Postman
     href: access-fhir-postman-tutorial.md
+  - name: Use SMART on FHIR proxy
+    href: use-smart-on-fhir-proxy.md
 - name: How-to guides
   expanded: false
   items:
+  - name: Register a resource application
+    href: register-resource-azure-ad-client-app.md
+  - name: Register a confidential client app
+    href: register-confidential-azure-ad-client-app.md
+  - name: Register a public client application
+    href: register-public-azure-ad-client-app.md
+  - name: Register a service client application
+    href: register-service-azure-ad-client-app.md
   - name: Configure database settings
     href: configure-database.md
   - name: Find identity object IDs
@@ -49,16 +57,8 @@
     href: use-custom-headers.md
   - name: Get a token for Azure API for FHIR - CLI
     href: get-healthcare-apis-access-token-cli.md
-  - name: Register a public client application
-    href: register-public-azure-ad-client-app.md
-  - name: Use SMART on FHIR proxy
-    href: use-smart-on-fhir-proxy.md
   - name: Configure CORS
     href: configure-cross-origin-resource-sharing.md
-  - name: Register a service client application
-    href: register-service-azure-ad-client-app.md
-  - name: Register a resource application
-    href: register-resource-azure-ad-client-app.md
 - name: Resources
   items:
   - name: FAQ

articles/healthcare-apis/register-confidential-azure-ad-client-app.md

@@ -5,7 +5,7 @@ services: healthcare-apis
 author: hansenms
 ms.service: healthcare-apis
 ms.subservice: fhir
-ms.topic: tutorial
+ms.topic: conceptual
 ms.date: 02/07/2019
 ms.author: mihansen
 ---

articles/healthcare-apis/register-resource-azure-ad-client-app.md

@@ -40,7 +40,7 @@ A resource application has an identifier URI (Application ID URI), which clients
 
 3. Enter the identifier URI and click **Save**. A good identifier URI would be the URI of your FHIR server.
 
-4. Click **Add a scope** and add any scopes that you would like to define for you API. Azure AD does not currently allow slashes (`/`) in scope names. We recommend using `$` instead. A scope like `patient/*.read` would be `patient$*.read`.
+4. Click **Add a scope** and add any scopes that you would like to define for your API. Azure AD does not currently allow slashes (`/`) in scope names. We recommend using `$` instead. A scope like `patient/*.read` would be `patient$*.read`.
 
     ![Audience and scope](media/how-to-aad/portal-aad-register-new-app-registration-AUD-SCOPE.png)
 
@@ -82,7 +82,7 @@ The Azure API for FHIR and the OSS FHIR Server for Azure use [Azure Active Direc
 
 ## Next steps
 
-In this article, you've learned how to register a resource application in Azure Active Directory. Next, deploy a FHIR API in Azure.
+In this article, you've learned how to register a resource application in Azure Active Directory. Next, deploy the Azure API for FHIR.
 
 >[!div class="nextstepaction"]
->[Deploy Open Source FHIR server](fhir-oss-powershell-quickstart.md)
+>[Deploy Azure API for FHIR](fhir-paas-powershell-quickstart.md)

articles/healthcare-apis/tutorial-1-decision-flow.md

@@ -32,7 +32,13 @@ If you're deploying FHIR Server for Azure (the OSS version), use this decision f
 
 In this tutorial, you've gone through the decision flow on how to register applications based on the version of the FHIR service you're deploying.
 
-You can now register a confidential client application and provision the FHIR service.
+Based on the decisions you made above, please see the how-to-guides to register your applications
+
+* [Register a resource application](register-resource-azure-ad-client-app.md)
+* [Register a confidential client application](register-confidential-azure-ad-client-app.md)
+* [Register a public client application](register-public-azure-ad-client-app.md)
+
+Once this is complete, you can deploy the Azure API for FHIR.
 
 >[!div class="nextstepaction"]
->[Register a confidential client app](register-confidential-azure-ad-client-app.md)
+>[Deploy Azure API for FHIR](fhir-paas-powershell-quickstart.md)