Skip to content

Commit 2049e42

Browse files
Merge pull request #212078 from whhender/updating-salesforce-guide
Connected App information
2 parents 5b83c27 + ffd86ee commit 2049e42

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/purview/register-scan-salesforce.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,9 @@ When setting up scan, you can choose to scan an entire Salesforce organization,
3434
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
3535
- An active [Microsoft Purview account](create-catalog-portal.md).
3636
- You need Data Source Administrator and Data Reader permissions to register a source and manage it in the Microsoft Purview governance portal. For more information about permissions, see [Access control in Microsoft Purview](catalog-permissions.md).
37+
- A Salesforce connected app, which will be used to access your Salesforce information.
38+
- If you need to create a connected app, you can follow the [Salesforce documentation](https://help.salesforce.com/s/articleView?id=sf.connected_app_create_basics.htm&type=5).
39+
- You will need to [enable OAuth for you Salesforce application](https://help.salesforce.com/s/articleView?id=sf.connected_app_create_api_integration.htm&type=5).
3740

3841
> [!NOTE]
3942
> **If your data store is not publicly accessible** (if your data store limits access from on-premises network, private network or specific IPs, etc.), **you will need to configure a self hosted integration runtime to connect to it**.
@@ -110,10 +113,10 @@ To create and run a new scan, follow these steps:
110113

111114
1. **Credential**: Select the credential to connect to your data source. Make sure to:
112115
* Select **Consumer key** while creating a credential.
113-
* Provide the username of the user that the connected app is imitating in the User name input field.
116+
* Provide the username of the user that the [connected app](#prerequisites) is imitating in the User name input field.
114117
* Store the password of the user that the connected app is imitating in an Azure Key Vault secret.
115118
* If your self-hosted integration runtime machine's IP is within the [trusted IP ranges for your organization](https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm&type=5) set on Salesforce, provide just the password of the user.
116-
* Otherwise, concatenate the password and security token as the value of the secret. The security token is an automatically generated key that must be added to the end of the password when logging in to Salesforce from an untrusted network. Learn more about how to [get or reset a security token](https://help.salesforce.com/apex/HTViewHelpDoc?id=user_security_token.htm).
119+
* Otherwise, **concatenate the password and security token as the value of the secret**. The security token is an automatically generated key that must be added to the end of the password when logging in to Salesforce from an untrusted network. Learn more about how to [get or reset a security token](https://help.salesforce.com/apex/HTViewHelpDoc?id=user_security_token.htm).
117120
* Provide the consumer key from the connected app definition. You can find it on the connected app's Manage Connected Apps page or from the connected app's definition.
118121
* Stored the consumer secret from the connected app definition in an Azure Key Vault secret. You can find it along with consumer key.
119122

0 commit comments

Comments
 (0)