Tate_Forgey Steve Goodman Tokin Blackford apologies on the delay. Below are some more details around how this runbook would work:
1.Human Resources enter details of the new employee using the on-boarding form (PowerApp)
2.On submission the specified Manager receives an approval request with the submitted details (Flow Approval)
3.The Manager adds any notes, such as additional equipment required, desk location, etc. and approves the request
4.Once approved the Flow (Flow + Azure AD)
a)Flow submits the details to Azure Automation runbooks that orchestrate on-premise hybrid worker servers to create Active Directory accounts
b)Synchronizes those accounts to Azure AAD
c)Create mailboxes
d)License the account as required including unified communications licenses and automatic assignment of Teams telephone numbers
e)The new account is configured with extended attributes based on service line, location, employee type, etc.
f)Dynamic AAD security groups add relevant accounts as members based on the extended attribute values automatically adding new employees to the correct distribution lists, Teams and Enterprise Applications configured in Azure.
g)The account is also enabled for Azure Multi Factor Authentication and Self-Service Password Reset - autopilot
5.The runbook returns a success result back to the Flow which then adds the account to any statically assigned AAD / O365 groups.
6.Notifications are sent by email to relevant parties and Microsoft Planner tasks are automatically assigned to Plans hosted in departmental Teams channels enabling a coordinated experience for the staff managing the employee on-boarding from reception to desk
7.Planner tasks are assigned to IT staff to supply requested equipment for the new employee including Intune managed devices that use Windows Autopilot for zero touch configuration of the device further enhancing the new employees on-boarding experience