Office 365 provisioning, ASP.NET CORE, ms graph API, Powershell

We are looking for a senior ASP.NET developer who can help us to improve our SaaS platform to automate provisioning cloud solutions. Your task objective is to develop the foundation of our security and identity management structures. The deliverable for this first task is to create modules that we can easily integrate into our main Visual Studio project. Our senior developer will help you to integrate the modules into our platform. The platform we are building will have two different types of target groups; ICT companies and customers of these ICT companies. With our SaaS platform, the ICT companies can simplify and automate provisioning, which will help the users to save time and to lower the complexity of provisioning cloud solutions. The customers of the ICT companies will also have access to the platform. They will see pages to self-service provisioning processes. Within our platform, we will have a marketplace containing platforms to which our platform can connect. Connecting to another platform needs to be done securely and structured based on the below multi and multitier tenancy Azure structure. Below is the child relationship shown between tenants to explain the basics of the user management structure for which you need to develop the foundation. Platform Admin (We) Tenant X | ICT company Y (Tenant Y) | ---------------------------------------------------- | | Customer A of ICT company Y Customer B of ICT company Y - Tenant A1 - Tenant A2 The user of ICT company Y needs to be able to manage the Azure tenants/ office 365 users of its child customers' tenants. In the above example, Customer, A, and Customer B are both customers of ICT company Y. So, when the user of company Y, with sufficient rights logs in to our platform, then this user needs to be able to manage for both customers (A and B) their tenants and child tenants. Task 1: Register &login ICT company and customer A User Develop a login page without any design based on SAML, SCIM protocol, OpenID Connect, OAuth 2.0, and Azure Tenant management. When the user logs in the first time, the user needs to see a window in which the user approves that his or her Azure account will be sharing some data with our platform. Task 3: ICT company assigns license to a new user A user called in this example "user A" of ICT company Y, with sufficient rights, logs in to our platform with his Azure credentials and goes to the Customer A account details page. On that page, the user clicks on the button called "Add a new employee." There will be some options to assign a new employee to an existing office 365 license. What the exact steps are to add a new employee, are irrelevant for your task objective. The only thing you need to do is: A. Make sure that "user A" has based on your login process the rights to manage office 365 accounts/Azure accounts for customer A and customer B and their child tenants. B. Create a simple button to assign a new user (Firstname, Lastname, UPN) to a license. Assign a license with Microsoft Graph to the new user. C. Create another simple button to assign a new user (Firstname, Lastname, UPN) to a license. But in this example, assign a license with Powershell to the new user. So based on your login process, the button needs to trigger a Powershell script. There are some Powershell scripts on Github to assign a license to a new user. D. The consuming of the Microsoft Graph API or executing Powershell scripts needs to be authorized based on multi-tenancy authorization. Task 4: Customer A sees all users connected to Company A tenant(s) Show after a user belonging to customer A logs in to the platform a list of users based on Azure Tenant management data. Task 5: Make a centralized Oauth structure for our market place Extend our marketplace pages with a standard OpenID Connect and OAuth 2.0 helper to connect the Azure account of the ICT company user to external platforms and to use a single sign-on.