Skip to content

Commit 56542c1

Browse files
committed
remove service principal auth type
1 parent ef8f78b commit 56542c1

File tree

1 file changed

+0
-47
lines changed

1 file changed

+0
-47
lines changed

articles/data-factory/connector-snowflake.md

Lines changed: 0 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,6 @@ This Snowflake connector supports the following authentication types. See the co
104104

105105
- [Basic authentication](#basic-authentication)
106106
- [Key pair authentication](#key-pair-authentication)
107-
- [Service Principal authentication](#service-principal-authentication)
108107

109108
### Basic authentication
110109

@@ -215,52 +214,6 @@ In addition to the generic properties that are described in the preceding sectio
215214
}
216215
```
217216

218-
### Service Principal authentication
219-
220-
To use **Service Principal** authentication, set up the Snowflake Service-to-Service (S2S) authentication environment referring to [How to configure Azure to issue OAuth tokens on behalf of a client to access Snowflake](https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself). Afterwards, make note of these values, which you use to define the linked service:
221-
222-
- Application (client) ID, which is **Client ID** in the linked service.
223-
- Client secret value, which is the **Client secret** in the linked service.
224-
- Tenant ID
225-
226-
In addition to the generic properties that are described in the preceding section, specify the following properties:
227-
228-
| Property | Description | Required |
229-
| :--------------- | :----------------------------------------------------------- | :------- |
230-
| tenantId | Specify the tenant information (domain name or tenant ID) under which your application resides. Retrieve it by hovering over the upper-right corner of the Azure portal. | Yes |
231-
| clientId | Specify the application's client ID. | Yes |
232-
| clientSecret | Specify the application's client secret value. | Yes |
233-
| scope | The scope of the access required. It describes what kind of access will be requested. | Yes |
234-
235-
**Example:**
236-
237-
```json
238-
{
239-
"name": "SnowflakeV2LinkedService",
240-
"properties": {
241-
"type": "SnowflakeV2",
242-
"typeProperties": {
243-
"accountIdentifier": "<accountIdentifier>",
244-
"database": "<database>",
245-
"warehouse": "<warehouse>",
246-
"authenticationType": "AADServicePrincipal",
247-
"tenantId": "<tenant ID>",
248-
"clientId": "<client ID>",
249-
"clientSecret": {
250-
"type": "SecureString",
251-
"value": "<client secret>"
252-
},
253-
"scope": "<scope>",
254-
"role": "<role>"
255-
},
256-
"connectVia": {
257-
"referenceName": "<name of Integration Runtime>",
258-
"type": "IntegrationRuntimeReference"
259-
}
260-
}
261-
}
262-
```
263-
264217
## Dataset properties
265218

266219
For a full list of sections and properties available for defining datasets, see the [Datasets](concepts-datasets-linked-services.md) article.

0 commit comments

Comments
 (0)