Postman fixes for ADF

Author: jonburchel

articles/data-factory/connector-http.md

@@ -42,7 +42,7 @@ You can use this HTTP connector to:
 - Copy the HTTP response as-is or parse it by using [supported file formats and compression codecs](supported-file-formats-and-compression-codecs.md).
 
 > [!TIP]
-> To test an HTTP request for data retrieval before you configure the HTTP connector, learn about the API specification for header and body requirements. You can use tools like Postman or a web browser to validate.
+> To test an HTTP request for data retrieval before you configure the HTTP connector, learn about the API specification for header and body requirements. You can use tools like Visual Studio, PowerShell's Invoke-RestMethod, or a web browser to validate.
 
 ## Prerequisites
 

articles/data-factory/connector-odata.md

@@ -358,21 +358,23 @@ Project Online requires user-based OAuth, which is not supported by Azure Data F
 
 1. Use **Postman** to get the access token:
 
-   1. Navigate to **Authorization** tab on the Postman Website.
-   1. In the **Type** box, select **OAuth 2.0**, and in the **Add authorization data to** box, select **Request Headers**.
-   1. Fill the following information in the **Configure New Token** page to get a new access token: 
-      - **Grant type**: Select **Authorization Code**.
-      - **Callback URL**: Enter `https://www.localhost.com/`. 
-      - **Auth URL**: Enter `https://login.microsoftonline.com/common/oauth2/authorize?resource=https://<your tenant name>.sharepoint.com`. Replace `<your tenant name>` with your own tenant name. 
-      - **Access Token URL**: Enter `https://login.microsoftonline.com/common/oauth2/token`.
-      - **Client ID**: Enter your Microsoft Entra service principal ID.
-      - **Client Secret**: Enter your service principal secret.
-      - **Client Authentication**: Select **Send as Basic Auth header**.
-     
-   1. You will be asked to sign in with your username and password.
-   1. Once you get your access token, please copy and save it for the next step.
-   
-    :::image type="content" source="./media/connector-odata/odata-project-online-postman-access-token-inline.png" alt-text="Screenshot of using Postman to get the access token." lightbox="./media/connector-odata/odata-project-online-postman-access-token-expanded.png":::        
+    > [!NOTE]
+    > Postman is a widely used applicatoin among developers for testing remote web APIs. However, there are some security and privacy risks associated with its usage. This article does not endorse the use of Postman for production environments. Please use it at your own risk.
+
+    1. Navigate to **Authorization** tab on the Postman Website.
+    1. In the **Type** box, select **OAuth 2.0**, and in the **Add authorization data to** box, select **Request Headers**.
+    1. Fill the following information in the **Configure New Token** page to get a new access token: 
+       - **Grant type**: Select **Authorization Code**.
+       - **Callback URL**: Enter `https://www.localhost.com/`.
+       - **Auth URL**: Enter `https://login.microsoftonline.com/common/oauth2/authorize?resource=https://<your tenant name>.sharepoint.com`. Replace `<your tenant name>` with your own tenant name. 
+       - **Access Token URL**: Enter `https://login.microsoftonline.com/common/oauth2/token`.
+       - **Client ID**: Enter your Microsoft Entra service principal ID.
+       - **Client Secret**: Enter your service principal secret.
+       - **Client Authentication**: Select **Send as Basic Auth header**.
+    1. You will be asked to sign in with your username and password.
+    1. Once you get your access token, please copy and save it for the next step.
+
+    :::image type="content" source="./media/connector-odata/odata-project-online-postman-access-token-inline.png" alt-text="Screenshot of using Postman to get the access token." lightbox="./media/connector-odata/odata-project-online-postman-access-token-expanded.png":::
 
 1. Create the OData linked service:
     - **Service URL**: Enter `https://<your tenant name>.sharepoint.com/sites/pwa/_api/Projectdata`. Replace `<your tenant name>` with your own tenant name. 

articles/data-factory/connector-rest.md

@@ -43,7 +43,7 @@ Specifically, this generic REST connector supports:
 - For REST as source, copying the REST JSON response [as-is](#export-json-response-as-is) or parse it by using [schema mapping](copy-activity-schema-and-type-mapping.md#schema-mapping). Only response payload in **JSON** is supported.
 
 > [!TIP]
-> To test a request for data retrieval before you configure the REST connector in Data Factory, learn about the API specification for header and body requirements. You can use tools like Postman or a web browser to validate.
+> To test a request for data retrieval before you configure the REST connector in Data Factory, learn about the API specification for header and body requirements. You can use tools like Visual Studio, PowerShell's Invoke-RestMethod or a web browser to validate.
 
 ## Prerequisites
 

articles/data-factory/connector-troubleshoot-rest.md

@@ -58,7 +58,7 @@ This article provides suggestions to troubleshoot common problems with the REST
 
     - Note that 'curl' might not be suitable to reproduce an SSL certificate validation issue. In some scenarios, the 'curl' command was executed successfully without encountering any SSL certificate validation issues. But when the same URL is executed in a browser, no SSL certificate is actually returned for the client to establish trust with server.
 
-      Tools like **Postman** and **Fiddler** are recommended for the preceding case.
+      Tools like **Fiddler** are recommended for the preceding case.
 
 ## Related content
 

articles/data-factory/data-factory-troubleshoot-guide.md

@@ -1076,7 +1076,7 @@ If the HDI activity is stuck in preparing for cluster, follow the guidelines bel
 
 - **Cause**: The request failed due to an underlying issue such as network connectivity, a DNS failure, a server certificate validation, or a timeout.
 
-- **Recommendation**: Use Fiddler/Postman/Netmon/Wireshark to validate the request.
+- **Recommendation**: Use Fiddler/Netmon/Wireshark to validate the request.
 
     **Using Fiddler**
     

articles/data-factory/security-and-access-control-troubleshoot-guide.md

@@ -227,7 +227,7 @@ CMK in the service should have "Soft Delete" enabled and "Purge Protect" enabled
 Please review [Recover deleted Key](../key-vault/general/key-vault-recovery.md?tabs=azure-portal#list-recover-or-purge-soft-deleted-secrets-keys-and-certificates) and [Deleted Key Value](../key-vault/general/key-vault-recovery.md?tabs=azure-portal#list-recover-or-purge-a-soft-deleted-key-vault)
 
 * User Assigned Managed Identity (UA-MI) was deleted before the service. 
-You can recover from this by using REST API calls, you can do this in an http client of your choice in any programming language. If you have not anything already set up for REST API calls with Azure authentication, the easiest way to do this would be by using POSTMAN/Fiddler. Please follow following steps.
+You can recover from this by using REST API calls, you can do this in an http client of your choice in any programming language. If you have not anything already set up for REST API calls with Azure authentication, the easiest way to do this would be by using Fiddler. Please follow following steps.
 
    1.  Make a GET call using Method: GET Url like   `https://management.azure.com/subscriptions/YourSubscription/resourcegroups/YourResourceGroup/providers/Microsoft.DataFactory/factories/YourFactoryName?api-version=2018-06-01`