Skip to content

Commit 7aed8d7

Browse files
committed
tenant also required for client creds login
1 parent c38dcd7 commit 7aed8d7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

vignettes/auth.Rmd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,10 @@ gr <- get_graph_login(tenant="yourtenant")
6565

6666
This is the scenario where you want to use AzureGraph as part of an automated script or unattended session, for example in a deployment pipeline. The appropriate authentication flow in this case is the client credentials flow.
6767

68-
For this scenario, you must have a custom app ID and client secret. On the client side, these are supplied in the `app` and `password` arguments; see later for creating the app registration on the server side.
68+
For this scenario, you must have a custom app ID and client secret. On the client side, these are supplied in the `app` and `password` arguments; see later for creating the app registration on the server side. You must also specify your tenant as AAD won't be able to detect it from a user's credentials.
6969

7070
```r
71-
gr <- create_graph_login(app="yourccappid", password="client_secret")
71+
gr <- create_graph_login(tenant="yourtenant", app="yourccappid", password="client_secret")
7272
```
7373

7474
In the non-interactive scenario, you don't use `get_graph_login()`; instead, you simply call `create_graph_login()` as part of your script.

0 commit comments

Comments
 (0)