<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Power Automate on JanBakker.tech</title><link>https://janbakker.tech/tags/power-automate/</link><description>Recent content in Power Automate on JanBakker.tech</description><generator>Hugo</generator><language>en-US</language><copyright>Jan Bakker</copyright><lastBuildDate>Fri, 02 Jun 2023 09:50:08 +0000</lastBuildDate><atom:link href="https://janbakker.tech/tags/power-automate/index.xml" rel="self" type="application/rss+xml"/><item><title>Send an email on a new Azure MFA method registration</title><link>https://janbakker.tech/send-an-email-on-a-new-azure-mfa-method-registration/</link><pubDate>Fri, 02 Jun 2023 09:50:08 +0000</pubDate><guid>https://janbakker.tech/send-an-email-on-a-new-azure-mfa-method-registration/</guid><description>&lt;p&gt;I&amp;rsquo;ve done quite some Azure MFA projects over time (and counting), and as we mainly focus on the technical side, there are also practical sides to consider. Every project has its own approach and challenges, and more importantly: the user is impacted more or less, and that asks for some guidance.&lt;/p&gt;</description></item><item><title>License on-demand with Power Automate and Azure AD</title><link>https://janbakker.tech/license-on-demand-with-power-automate-and-azure-ad/</link><pubDate>Sun, 18 Oct 2020 15:49:41 +0000</pubDate><guid>https://janbakker.tech/license-on-demand-with-power-automate-and-azure-ad/</guid><description>&lt;p&gt;Most organizations are using &#10;&lt;a href="https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-licensing-whatis-azure-portal" rel="noopener"&gt;group-based&lt;/a&gt; licensing in Azure Active Directory. This is often integrated with the onboarding process of the users. But there are some use cases where you have some non-standard licenses attached to your tenant that you hand out on demand. You could still use group-based licensing, but users are added manually to the group.&lt;/p&gt;</description></item><item><title>Use Microsoft Graph Security for end-user notifications</title><link>https://janbakker.tech/use-microsoft-graph-security-for-end-user-notifications/</link><pubDate>Wed, 19 Aug 2020 13:11:23 +0000</pubDate><guid>https://janbakker.tech/use-microsoft-graph-security-for-end-user-notifications/</guid><description>&lt;p&gt;In this short blog post, I want to show how you can use the Microsoft Graph Security to send alerts and notifications to your end-users. I also want to show you that it is super easy to set up. All you need is:&lt;/p&gt;</description></item><item><title>Bulk dismiss risky users with Power Automate or Logic Apps</title><link>https://janbakker.tech/bulk-dismiss-risky-users-with-power-automate-or-logic-apps/</link><pubDate>Thu, 06 Aug 2020 07:48:02 +0000</pubDate><guid>https://janbakker.tech/bulk-dismiss-risky-users-with-power-automate-or-logic-apps/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update 08-10-2020:&lt;/strong&gt;&lt;/em&gt; Microsoft released an &#10;&lt;a href="https://docs.microsoft.com/en-us/connectors/azureadip/" rel="noopener"&gt;official connector for Azure AD Identity Protection&lt;/a&gt;. This would be much easier to use, since you don&amp;rsquo;t have to create a service principal to authenticate the custom connector. However, at the time of writing the official connector does not have the action to get all the risky users. Will keep an eye on things.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>Prepopulate phone methods using a Custom Connector in Power Automate</title><link>https://janbakker.tech/prepopulate-phone-methods-using-a-custom-connector-in-power-automate/</link><pubDate>Thu, 30 Jul 2020 07:30:00 +0000</pubDate><guid>https://janbakker.tech/prepopulate-phone-methods-using-a-custom-connector-in-power-automate/</guid><description>&lt;p&gt;This blog post shows the custom connector that is built on top of the Microsoft Graph API. With this connector, you can do bulk actions on Azure AD and provision phone numbers for your users. They can be used for MFA and SSPR. To understand how the connector works, please also read the first part of the blog where I explain the API in detail. In the second part, I have added a step-step-guide on how to create the custom connector and use it in an automation flow.&lt;/p&gt;</description></item><item><title>Prepopulate phone methods for MFA and SSPR using Graph API</title><link>https://janbakker.tech/prepopulate-phone-methods-for-mfa-and-sspr-using-graph-api/</link><pubDate>Thu, 30 Jul 2020 07:29:00 +0000</pubDate><guid>https://janbakker.tech/prepopulate-phone-methods-for-mfa-and-sspr-using-graph-api/</guid><description>&lt;p&gt;This blog post shows the custom connector that is built on top of the Microsoft Graph API. With this connector, you can do bulk actions on Azure AD and provision phone numbers for your users. They can be used for MFA and SSPR. To understand how the connector works, please also read the first part of the blog where I explain the API in detail. In the second part, I have added a step-step-guide on how to create the custom connector and use it in an automation flow.&lt;/p&gt;</description></item><item><title>Use Power Automate as your Conditional Access Police Department</title><link>https://janbakker.tech/use-power-automate-as-your-ca-police-department/</link><pubDate>Sat, 04 Jul 2020 07:10:42 +0000</pubDate><guid>https://janbakker.tech/use-power-automate-as-your-ca-police-department/</guid><description>&lt;p&gt;Last week, I was working on a &#10;&lt;a href="https://janbakker.tech/microsoft-secure-score-series-14-designate-more-than-one-global-admin/"&gt;new blog for the Secure Score Series&lt;/a&gt; regarding global admin and break glass accounts. I came to the point where I was thinking of possible scenarios that could go wrong with these accounts. What if someone accidentally added these users to a certain group? What if that group would be triggered in some policy or maintenance tasks? A lot of these actions can be discovered using Microsoft Cloud App Security and Azure Monitor. This way, you will be alerted when someone touches the accounts in any way, or if the account is used to sign-in.&lt;/p&gt;</description></item><item><title>Use Power Automate or Logic Apps to keep an eye on your licenses</title><link>https://janbakker.tech/use-power-automate-or-logic-apps-to-keep-an-eye-on-your-licenses/</link><pubDate>Sat, 27 Jun 2020 18:37:43 +0000</pubDate><guid>https://janbakker.tech/use-power-automate-or-logic-apps-to-keep-an-eye-on-your-licenses/</guid><description>&lt;p&gt;I guess we&amp;rsquo;ve all been there; you ran out of licenses in your Azure AD or Office 365 tenant. Despite you hang out in your admin portal every day, you were still taken by surprise when you discover an issue, caused by a license shortage. More often this is caused by the fact that the people who are responsible to buy these licenses, are not always IT admins. So it&amp;rsquo;s easy to run out of licenses. Time to get this fixed.&lt;/p&gt;</description></item><item><title>Use Power Automate for your custom "dynamic" groups</title><link>https://janbakker.tech/use-power-automate-for-your-custom-dynamic-groups/</link><pubDate>Wed, 01 Apr 2020 19:52:46 +0000</pubDate><guid>https://janbakker.tech/use-power-automate-for-your-custom-dynamic-groups/</guid><description>&lt;h2 id="azure-ad-dynamic-groups"&gt;Azure AD Dynamic Groups&lt;a class="anchor" href="#azure-ad-dynamic-groups" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Dynamic groups in Azure AD are awesome. I use them a lot. Dynamic groups can create groups based on attributes. For example, you can create a group that includes all the users from the Sales Team. The query for the group would look like this:&lt;/p&gt;</description></item></channel></rss>