As I mentioned in the beginning of this blog post, I previously wrote a blog post on how to set up an App Registration for a custom connector for PowerApps and Flows. I will now build on this, so if you want to follow the steps I do here, please set up the prerequisites as described in the blog post: -microsoft-graph-api-using-custom-connector-in-powerapps-and-flows/.
The next step is to implement the automated workflow for the onboarding process. We are going to use Microsoft Flow to achieve this. Based on our process diagram, submission of the form should trigger an approval request email to the hiring manager. In this example, the hiring manager is specified in the Supervisor field of the SharePoint form.
Microsoft Flow and Azure AD – let’s automate!
Microsoft Graph is an API developed to simplify access to objects, such as users and groups, and resources in the Azure cloud and the Office 365/Microsoft 365 platform. An app using Graph API uses its own identity to get access tokens from Azure AD, which allows the app to run on its own without user intervention. Used in tandem with a Power Automate flow, Graph API lets administrators develop automated workflows to generate reports, such as listing all the organization's Microsoft 365 groups, or trigger an action when an event occurs, such as sending a notification when certain files are modified.
I love Microsoft Flow. Its central part of Office 365 automation really helps the user to build quick and simple automated processes. Flow is low code or no code, meaning that you do most of the flow design by clicking and dragging parts of the flow and connects them together.
Formerly known as Microsoft Flow, Power Automate is a web-based service that helps to create automated workflows between your favorite apps and services to synchronize files, get notifications, collect data and more. Power Automate is a part of the Office 365 suite and is available in most Office 365 subscriptions. While its new name does not roll off the tongue quite like the old one did, it certainly flows (pun intended) with the Power Platform.
With minimal effort, we were able to get a working UI flow to be recorded, have it invoked from an automated flow, and the automated flow to handle the data intake submitted from the Microsoft Forms. You may have reasons for and against using Access database. Here, I used Access, to show you that you can collect data externally and store it in an internal database.
As you can see the reset was initiated by fim_password_service@support.onmicrosoft.com. This is an internal account that will be used for resetting the password in the Core Directory (as part of an authorized/valid SSPR request). All other events will be recorded as initiated by the username which was entered as part of the SSPR user flow.
Entitlement Management (ELM) is an Identity Governance feature in Azure AD that can manage identity and access lifecycle in an organization with the use of automated workflows for requests, approvals, assignments, reviews and expiration of access permissions.
Now we have created the complete flow and saved the Power Automate or flow. The time to test the Power automate (Flow) and check if it is working fine.
So Above we discussed, call the azure function from power automate (ms flow) with Authentication as none. But as security is very much important, We will discuss here How to Call Azure Function From Power automate With OAuth. 2ff7e9595c
Comments