An ASP.NET Core 1.0 website with Google Material Design, Azure Active Directory Graph API and Azure Automation Runbooks for managing Azure Active Directory in an easy controlled way.

• 01-08-2017 Initial release to GitHub
• 15-08-2017 Update ReadMe
• 24-10-2017 Migrate to NET Core 2

The front office or HR controls the onboarding of new employees. This easy AAD User and groups manager app supports the onboarding and changing roles of employees. Without the need of getting in to the technical, and complex, Azure portal by HR people.

The App separates responsibilities during the creation of AAD users and Groups in two areas. The front office triggers the creation or editing of a user and assigns groups via the App. the backoffice, AAD administrators, controls the steps and details needed for the creation of the user or group.

Solution roles:

The Web App uses several Cloud resources.

• Azure Web App, for the end user.

  • Create, edit, delete users and groups.
  • Triggers Azure Automation runbooks.
  • Collect user and group state via AAD Graph API.

• Azure Automation Runbook, maintained by administrators.

  • Edit, Create, Delete users or groups.
  • Send notification mail with temporally password.
  • Logs activity to Azure Blob Storage.

• Azure Blob Storage.

  • Stores application and runbook logdata.
  • Stores temporaly user and group data.

• Azure Active Directory

  • Holds users and groups
  • Secures Web App and Azure Automation Runbook.

All Azure Resources are created via ARM templates except AAD and its settings. These settings are the registration of the WebApp and the initial group configuration. See RBAC model for Azure AD.

The ARM templates follow the organization of Core and Application resources. See CICD for a cloud native services based system on Azure. The ARM Templates can be found in the ARM folder.

Google Material Design Lite is used for the UI.

The create user screen constructs the mail address from firstname, suffix, lastname via a simple JavaScript function, change this if you want something else. There should be at least one department group in AAD for the creation of a user.

The groupmembership editing screen collects all AAD groups with prefix 'Dep', 'Az' or 'App'. See file AadCollectieFromAad.cs

The Web Application is implemented with ASP Net Core in Visual Studio 2017 Preview. The solution is organized in Controllers, Business Services and Data Services with the default Dependency Injection of ASP Net Core 1.0.

Authentication of users is done with Azure Active Directory.

app.UseOpenIdConnectAuthentication(new OpenIdConnectOptions
            {
                ClientId = Configuration["Authentication:AzureAd:ClientId"],
                Authority = Configuration["Authentication:AzureAd:AADInstance"] + Configuration["Authentication:AzureAd:TenantId"],
                CallbackPath = Configuration["Authentication:AzureAd:CallbackPath"]
            });

Within Azure Active Directory users are restricted by application group who can use the App.

The Application Settings are holding the authentication settings, webhooks urls and storage account connection string. Default ASP Net Core appsetings.{environment}.json files are used for the different stages. An entry in the gitignore takes care no configuration settings are stored in GitHub.

The provisioning of the Cloud Resources is separated in Core Cloud resources and Application Cloud resousrces. Core are the App Service Plan, Storage Account, Azure Automation Runbooks. The application resource is the WebApp. Core resources need to be deployed first.

Three steps needs to be done before starting the WebApp.

• Deploy Core Azure Resource ARM Templates, and capture the configuration settings.
• Create or select Azure Active Directory.
• Add Application to Azure Active Directory, one entry for localhost on for deployed WebApp.

Run Application.

Pull requests serve as the primary mechanism by which contributions are proposed and accepted. We recommend creating a topic branch and sending a pull request to the master branch from the topic branch. For additional guidance, read through the GitHub Flow Guide.

Be prepared to address feedback on your pull request and iterate if necessary.