Azure API for FHIR document update for postman removal

Shashank Narang · Shashank Narang · commit 6581930c167c · 2025-01-30T12:19:22.000+05:30
diff --git a/articles/healthcare-apis/azure-api-for-fhir/register-confidential-azure-ad-client-app.md b/articles/healthcare-apis/azure-api-for-fhir/register-confidential-azure-ad-client-app.md
@@ -44,7 +44,7 @@ To register a new confidential client application, use the following steps.
 Permissions for Azure API for FHIR are managed through role-based access control (RBAC). For more details, visit [Configure Azure RBAC for FHIR](configure-azure-rbac.md).
 
 >[!NOTE]
->Use a  `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman. For more details, visit [Testing the FHIR API on Azure API for FHIR](tutorial-web-app-test-postman.md).
+>Use a  `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman.
 
 
 ## Application secret
@@ -67,9 +67,9 @@ Permissions for Azure API for FHIR are managed through role-based access control
 ## Next steps
 
 In this article, you were guided through the steps of how to register a confidential client application in the Microsoft Entra ID. You were also guided through the steps of how to add API permissions in Microsoft Entra ID for Azure API for FHIR. Lastly, you were shown how to create an application secret.<br>
-You can also learn how to access your FHIR server using Postman.
+You can also learn how to access your FHIR server using REST Client.
  
 >[!div class="nextstepaction"]
->[Access the FHIR service using Postman](./../fhir/use-postman.md)
+>[Access the FHIR service using REST Client](./../fhir/using-rest-client.md)
 
 [!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app.md b/articles/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app.md
@@ -54,7 +54,7 @@ To configure your [desktop](../../active-directory/develop/scenario-desktop-app-
 Permissions for Azure API for FHIR are managed through role-based access control (RBAC). For more details, visit [Configure Azure RBAC for FHIR](configure-azure-rbac.md).
 
 >[!NOTE]
->Use a `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman. For more details, visit [Testing the FHIR API on Azure API for FHIR](tutorial-web-app-test-postman.md).
+>Use a `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman.
 
 ## Validate FHIR server authority
 If the application you registered and your FHIR server are in the same Microsoft Entra tenant, you're good to proceed to the next steps.
@@ -63,9 +63,9 @@ If you configure your client application in a different Microsoft Entra tenant f
 
 ## Next steps
 
-In this article, you learned how to register a public client application in Microsoft Entra ID. Next, test access to your FHIR Server using Postman.
+In this article, you learned how to register a public client application in Microsoft Entra ID. Next, test access to your FHIR Server using REST Client.
  
 >[!div class="nextstepaction"]
->[Access the FHIR service using Postman](./../fhir/use-postman.md)
+>[Access the FHIR service using REST Client](./../fhir/using-rest-client.md)
 
 [!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md b/articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md
@@ -38,7 +38,7 @@ Follow these steps to create a new service client.
 Permissions for Azure API for FHIR are managed through role-based access control (RBAC). For more details, visit [Configure Azure RBAC for FHIR](configure-azure-rbac.md).
 
 >[!NOTE]
->Use a `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman. For more details, visit [Testing the FHIR API on Azure API for FHIR](tutorial-web-app-test-postman.md).
+>Use a `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman.
 
 ## Application secret
 
@@ -55,9 +55,9 @@ The service client needs a secret (password) to obtain a token.
 
 ## Next steps
 
-In this article, you learned how to register a service client application in Microsoft Entra ID. Next, test access to your FHIR server using Postman.
+In this article, you learned how to register a service client application in Microsoft Entra ID. Next, test access to your FHIR server using REST Client.
  
 >[!div class="nextstepaction"]
->[Access the FHIR service using Postman](./../fhir/use-postman.md)
+>[Access the FHIR service using REST Client](./../fhir/using-rest-client.md)
 
 [!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md b/articles/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md
@@ -102,7 +102,7 @@ Add the reply URL to the public client application that you created earlier for
 
 ### Step 3: Get a test patient
 
-To test the Azure API for FHIR and the SMART on FHIR proxy, you need to have at least one patient in the database. If you haven't interacted with the API yet, and you don't have data in the database, see [Access the FHIR service using Postman](./../fhir/use-postman.md) to load a patient. Make a note of the ID of a specific patient.
+To test the Azure API for FHIR and the SMART on FHIR proxy, you need to have at least one patient in the database. If you haven't interacted with the API yet, and you don't have data in the database, see [Access the FHIR service using REST Client](./../fhir/using-rest-client.md) to load a patient. Make a note of the ID of a specific patient.
 
 ### Step 4: Download the SMART on FHIR app launcher
 
diff --git a/articles/healthcare-apis/azure-api-for-fhir/toc.yml b/articles/healthcare-apis/azure-api-for-fhir/toc.yml
@@ -38,9 +38,7 @@
       href: tutorial-web-app-fhir-server.md
     - name: 2. Register public client application
       href: tutorial-web-app-public-app-reg.md
-    - name: 3. Test setup with Postman
-      href: tutorial-web-app-test-postman.md
-    - name: 4. Write web application
+    - name: 3. Write web application
       href: tutorial-web-app-write-web-app.md
   - name: SMART on FHIR 
     href: smart-on-fhir.md
diff --git a/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-fhir-server.md b/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-fhir-server.md
@@ -20,15 +20,14 @@ In this tutorial, you deploy a small JavaScript app which reads data from a FHIR
 
 1. Deploy a FHIR server
 1. Register a public client application
-1. Test access to the application
 1. Create a web application that reads this FHIR data
 
 ## Prerequisites
 
 You need the following before starting this set of tutorials.
 1. An Azure subscription
 1. A Microsoft Entra tenant
-1. [Postman](https://www.getpostman.com/) installed
+
 
 > [!NOTE]
 > For this tutorial, the FHIR service, Microsoft Entra application, and Microsoft Entra users are all in the same Microsoft Entra tenant. If this is not the case, you can still follow along with this tutorial, but may need to dive into some of the referenced documents to do additional steps.
diff --git a/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-public-app-reg.md b/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-public-app-reg.md
@@ -19,7 +19,7 @@ In the previous tutorial, you deployed and set up your Azure API for FHIR&reg;.
 1. Navigate to Microsoft Entra ID
 1. Select **App Registration** --> **New Registration**
 1. Name your application
-1. Select **Public client/native (mobile & desktop)** and set the redirect URI to `https://www.getpostman.com/oauth2/callback`.
+1. Select **Public client/native (mobile & desktop)** and set the redirect URI.
 
    :::image type="content" source="media/tutorial-web-app/register-public-app.png" alt-text="Screenshot of the Register an application pane, and an example application name and redirect URL.":::
 
@@ -55,9 +55,11 @@ Now that you have set up the correct authentication, set the API permissions.
 
 ## Next Steps
 
-You now have a public client application. In the next tutorial, we’ll walk through testing and gaining access to this application through Postman.
+You now have a public client application.
+There are tools available such as Postman that can allow intuitive querying.
+Once you have successfully connect to your client application, you’re ready to write your web application.
 
 >[!div class="nextstepaction"]
->[Test client application in Postman](tutorial-web-app-test-postman.md)
+>[Write a web application](tutorial-web-app-write-web-app.md)
 
 [!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-test-postman.md b/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-test-postman.md
diff --git a/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-write-web-app.md b/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-write-web-app.md
@@ -146,7 +146,7 @@ From here, you can go back to your web application resource and open the URL fou
 
 ## Next Steps
 
-You’ve successfully deployed the Azure API for FHIR, registered a public client application, tested access, and created a small web application. As a next step, check out the Azure API for FHIR supported features.
+You’ve successfully deployed the Azure API for FHIR, registered a public client application, and created a small web application. As a next step, check out the Azure API for FHIR supported features.
 
 >[!div class="nextstepaction"]
 >[Supported Features](fhir-features-supported.md)
