<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Groups on JanBakker.tech</title><link>https://janbakker.tech/tags/groups/</link><description>Recent content in Groups on JanBakker.tech</description><generator>Hugo</generator><language>en-US</language><copyright>Jan Bakker</copyright><lastBuildDate>Sat, 16 Jan 2021 13:58:38 +0000</lastBuildDate><atom:link href="https://janbakker.tech/tags/groups/index.xml" rel="self" type="application/rss+xml"/><item><title>Self Service in Microsoft 365</title><link>https://janbakker.tech/self-service-in-microsoft-365/</link><pubDate>Sat, 16 Jan 2021 13:58:38 +0000</pubDate><guid>https://janbakker.tech/self-service-in-microsoft-365/</guid><description>&lt;p&gt;One of the great things about Azure Active Directory is the capability of self-service. Maintaining security groups can be a laborious and cumbersome task to do. The same applies to resetting passwords, handing out licenses, permissions, applications, and privileged roles. What if I told you that you can delegate most of these tasks to your end-users, their managers, or product-and application owners? In this blog post, I will show you the built-in capabilities of self-service in Azure Active Directory, which is underlying to Microsoft 365. Some of them you might already know, some might be new to you.&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 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>