Skip to content

Latest commit

 

History

History
101 lines (63 loc) · 5.03 KB

File metadata and controls

101 lines (63 loc) · 5.03 KB

Day NN - Scenario Template

When adding Images, save them in the Images folder for your day

Prerequisites

To complete this sample you need the following:

  • Complete the Base Console Application Setup
  • Visual Studio Code installed on your development machine. If you do not have Visual Studio Code, visit the previous link for download options. (Note: This tutorial was written with Visual Studio Code version 1.52.1. The steps in this guide may work with other versions, but that has not been tested.)
  • .Net Core SDK. (Note This tutorial was written with .Net Core SDK 5.0.101. The steps in this guide may work with other versions, but that has not been tested.)
  • C# extension for Visual Studio Code
  • Either a personal Microsoft account with a mailbox on Outlook.com, or a Microsoft work or school account.

If you don't have a Microsoft account, there are a couple of options to get a free account:

Step 1: Update the App Registration permissions

As this exercise requires new permissions the App Registration needs to be updated to include the <New-Permission-Here> permission using the new Azure AD Portal App Registrations UI.

  1. Open a browser and navigate to the App registrations page within the Azure AD Portal. Login using a personal account (aka: Microsoft Account) or Work or School Account with permissions to create app registrations.

    Note: If you do not have permissions to create app registrations contact your Azure AD domain administrators.

  2. Click on the .NET Core Graph Tutorial item in the list

    Note: If you used a different name while completing the Base Console Application Setup select that instead.

  3. Click API permissions from the current blade content.

    1. Click Add a permission from the current blade content.

    2. On the Request API permissions flyout select Microsoft Graph.

      Screenshot of selecting Microsoft Graph permission to add to app registration

    3. Select [Application|Delegated] permissions.

    4. In the "Select permissions" search box type "<Start of permission string>".

    5. Select <New-Permission-Here> from the filtered list.

      Screenshot of adding [application|delegated] permission for User.Read.All permission

    6. Click Add permissions at the bottom of flyout.

  4. Back on the API permissions content blade, click Grant admin consent for <name of tenant>. need new screenshot here Screenshot of granting admin consent for newly added permission

    1. Click Yes.

Step 2: Extend the app to yyy

In this step you will create a UserHelper class that encapsulates the logic for creating users and finding user objects by alias and then add calls to the console application created in the Base Console Application Setup to provision a new user.

Create the MyHelper class

  1. Create a new file in the Helpers folder called MyHelperFileName.cs.

  2. Replace the contents of MyHelperFileName.cs with the following code:

    // Your code here

This class contains the code to ....

Extend program to yyy

  1. Inside the Program class add a new method YourMethod with the following definition. This method creates a new User in Azure Active Directory using the UserHelper class. This user will enableded and be required to change their password upon their next login.

    // Your code here

    Important Any key things to note where the developer might run into issues.

  2. Continuing in the Main method add the following code to call the new method.

    YourMethod();
  3. Save all files.

The console application is now able to <do some new thing>. In order to test the console application run the following commands from the command line:

dotnet build
dotnet run

Summary of what the thing that can be done is.