-
Using Microsoft Graph Developer Tool: https://learn.microsoft.com/en-us/graph/tutorials/dotnet?tabs=aad&source=docs
-
Code submission for use with M365 Developer Account Client ID [email protected] Used to automatically register a new application in the Microsoft Application Registration portal and embed the client ID (also known as the app ID) into the code sample.
- Please read the README.md on how to run the completed project. Thank you folks in the time permitted. Build and run the sample
- NOTE: In your command-line interface (CLI), navigate to the project directory and run the following commands. In your command-line interface (CLI), navigate to the project directory and run the following commands.
dotnet restore
dotnet build
dotnet run
To run the completed project in this folder, you need the following:
- The .NET SDK installed on your development machine. (Note: This tutorial was written with .NET SDK version 6.0.102. The steps in this guide may work with other versions, but that has not been tested.)
- A Microsoft work or school account.
If you don't have a Microsoft account, you can sign up for the Microsoft 365 Developer Program to get a free Microsoft 365 subscription.
You can register an application using the Azure Active Directory admin center, or by using the Microsoft Graph PowerShell SDK.
NOTE: If you downloaded this code from https://developer.microsoft.com/graph/quick-start, an app registration has already been created for you. However, if you want to use the app-only portion of this sample, you will need to modify the app registration as specified in Configure app-only auth (AAD admin center) or Configure app-only auth (PowerShell).
-
Open a browser and navigate to the Azure Active Directory admin center and login using a personal account (aka: Microsoft Account) or Work or School Account.
-
Select Azure Active Directory in the left-hand navigation, then select App registrations under Manage.
-
Select New registration. Enter a name for your application, for example,
.NET Graph Tutorial
. -
Set Supported account types as desired. The options are:
Option Who can sign in? Accounts in this organizational directory only Only users in your Microsoft 365 organization Accounts in any organizational directory Users in any Microsoft 365 organization (work or school accounts) Accounts in any organizational directory ... and personal Microsoft accounts Users in any Microsoft 365 organization (work or school accounts) and personal Microsoft accounts -
Leave Redirect URI empty.
-
Select Register. On the application's Overview page, copy the value of the Application (client) ID and save it, you will need it in the next step. If you chose Accounts in this organizational directory only for Supported account types, also copy the Directory (tenant) ID and save it.
-
Select Authentication under Manage. Locate the Advanced settings section and change the Allow public client flows toggle to Yes, then choose Save.
Note: This section requires a work/school account with the Global administrator role. You only need to complete these steps if you plan on using the app-only portions of this sample.
-
Select API permissions under Manage.
-
Remove the default User.Read permission under Configured permissions by selecting the ellipses (...) in its row and selecting Remove permission.
-
Select Add a permission, then Microsoft Graph.
-
Select Application permissions.
-
Select User.Read.All, then select Add permissions.
-
Select Grant admin consent for..., then select Yes to provide admin consent for the selected permission.
-
Select Certificates and secrets under Manage, then select New client secret.
-
Enter a description, choose a duration, and select Add.
-
Copy the secret from the Value column, you will need it in the next steps.
To use PowerShell, you'll need the Microsoft Graph PowerShell SDK. If you do not have it, see Install the Microsoft Graph PowerShell SDK for installation instructions.
-
Open PowerShell and run the RegisterAppForUserAuth.ps1 file with the following command, replacing <audience-value> with the desired value (see table below).
Note: The RegisterAppForUserAuth.ps1 script requires a work/school account with the Application administrator, Cloud application administrator, or Global administrator role.
.\RegisterAppForUserAuth.ps1 -AppName ".NET Graph Tutorial" -SignInAudience <audience-value>
SignInAudience value Who can sign in? AzureADMyOrg
Only users in your Microsoft 365 organization AzureADMultipleOrgs
Users in any Microsoft 365 organization (work or school accounts) AzureADandPersonalMicrosoftAccount
Users in any Microsoft 365 organization (work or school accounts) and personal Microsoft accounts PersonalMicrosoftAccount
Only personal Microsoft accounts -
Copy the Client ID and Auth tenant values from the script output. You will need these values in the next step.
SUCCESS Client ID: 2fb1652f-a9a0-4db9-b220-b224b8d9d38b Auth tenant: common
Note: This section requires a work/school account with the Global administrator role. You only need to complete these steps if you plan on using the app-only portions of this sample.
-
Run the UpdateAppForAppOnlyAuth.ps1 file with the following command, replacing <your-client-id> with your client ID.
.\UpdateAppForAppOnlyAuth.ps1 -AppId <your-client-id> -GraphScopes "User.Read.All"
-
Copy the Tenant ID and Client secret values from the script output. You will need these values in the next step.
SUCCESS Tenant ID: a795ad0f-7d82-4a3b-a2c0-0713ec72ade7 Client secret: 2jv7Q~8eiOd_QafJ..... Secret expires: 2/16/2024 9:32:09 PM
-
Open appsettings.json and update the values according to the following table.
Setting Value clientId
The client ID of your app registration tenantId
The tenant ID of your organization (only needed if doing app-only) authTenant
If you chose the option to only allow users in your organization to sign in, change this value to your tenant ID. Otherwise leave as common
. -
Initialize the .NET development secret store by opening your CLI in the directory that contains GraphTutorial.csproj and running the following command.
dotnet user-secrets init
-
Add your client secret to the secret store using the following command, replacing <client-secret> with your client secret.
dotnet user-secrets set settings:clientSecret <client-secret>
Note: The .NET Secret Manager is only available during development. Production apps should store client secrets in a secure store, such as Azure Key Vault.
In your command-line interface (CLI), navigate to the project directory and run the following commands.
dotnet restore
dotnet build
dotnet run
Tags #hack-together and #microsoft-graph-sdk