<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://blue-sky-041ab6803.azurestaticapps.net/</id><title>Gudszent's How-to</title><subtitle>Azure, Mikrotik,powershell, scripts, openHAB, SmartHome.</subtitle> <updated>2026-03-16T23:53:16+01:00</updated> <author> <name>Gudszent Otto</name> <uri>https://blue-sky-041ab6803.azurestaticapps.net/</uri> </author><link rel="self" type="application/atom+xml" href="https://blue-sky-041ab6803.azurestaticapps.net/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://blue-sky-041ab6803.azurestaticapps.net/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Gudszent Otto </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Native Tenant Restrictions for Multi-Tenant Apps</title><link href="https://blue-sky-041ab6803.azurestaticapps.net/posts/Limit-SPN-tenant/" rel="alternate" type="text/html" title="Native Tenant Restrictions for Multi-Tenant Apps" /><published>2026-03-01T07:00:00+01:00</published> <updated>2026-03-01T07:00:00+01:00</updated> <id>https://blue-sky-041ab6803.azurestaticapps.net/posts/Limit-SPN-tenant/</id> <content src="https://blue-sky-041ab6803.azurestaticapps.net/posts/Limit-SPN-tenant/" /> <author> <name>gudszent</name> </author> <category term="Azure" /> <summary>In Preview, Microsoft just presented a new feature to restrict SPN access to specific tenants. If you’ve ever managed a multi-tenant app, you know the struggle. Usually, “multi-tenant” is an all-or-nothing deal—either the whole world can try to sign in, or nobody can. To lock it down to just your partners, you usually had to write custom code to check the “Issuer” claim. Well, those days are (...</summary> </entry> <entry><title>Global Secure Access for Private Network</title><link href="https://blue-sky-041ab6803.azurestaticapps.net/posts/GSA-Private-network/" rel="alternate" type="text/html" title="Global Secure Access for Private Network" /><published>2026-02-20T07:00:00+01:00</published> <updated>2026-02-20T07:00:00+01:00</updated> <id>https://blue-sky-041ab6803.azurestaticapps.net/posts/GSA-Private-network/</id> <content src="https://blue-sky-041ab6803.azurestaticapps.net/posts/GSA-Private-network/" /> <author> <name>gudszent</name> </author> <category term="Azure" /> <category term="Security" /> <category term="Network" /> <summary>I beleive, one of the most important things the good userexperience. We should build the world best architected solutions, but if the user experience is bad, nobody will use it. When I build a solution, I always try to make it as simple as possible for the users and maximize the user experience. Just like with GSA, if I want to reach my private endpoints, I want to reach them on the shortest wa...</summary> </entry> <entry><title>Open the tenant directly to the user</title><link href="https://blue-sky-041ab6803.azurestaticapps.net/posts/Direct-open-tenant/" rel="alternate" type="text/html" title="Open the tenant directly to the user" /><published>2026-01-26T07:00:00+01:00</published> <updated>2026-01-26T07:00:00+01:00</updated> <id>https://blue-sky-041ab6803.azurestaticapps.net/posts/Direct-open-tenant/</id> <content src="https://blue-sky-041ab6803.azurestaticapps.net/posts/Direct-open-tenant/" /> <author> <name>gudszent</name> </author> <category term="Azure" /> <summary>Time to time I loose access to different tenants. We finish projects, we move on to other projects, and sometime I forget that tenant my default tenant. So when I open the Azure portal, I am in a loop of “You don’t have access to this tenant”, and that not allow me to switch to the tenant I want to work with. So I have to open the tenant directly, and then I can switch to the tenant I want to w...</summary> </entry> <entry><title>Restrict MFA registration to compliant devices — Entra Conditional Access</title><link href="https://blue-sky-041ab6803.azurestaticapps.net/posts/MFA-Reg-Trusted-Device/" rel="alternate" type="text/html" title="Restrict MFA registration to compliant devices — Entra Conditional Access" /><published>2026-01-20T07:00:00+01:00</published> <updated>2026-03-16T21:46:26+01:00</updated> <id>https://blue-sky-041ab6803.azurestaticapps.net/posts/MFA-Reg-Trusted-Device/</id> <content src="https://blue-sky-041ab6803.azurestaticapps.net/posts/MFA-Reg-Trusted-Device/" /> <author> <name>gudszent</name> </author> <category term="Azure" /> <category term="Identity" /> <category term="Security" /> <summary>To restrict Multifactor Authentication (MFA) registration so it can only be completed from managed, trusted devices, create a Microsoft Entra Conditional Access policy that targets the “Register security information” user action and requires devices to be marked as compliant (Intune). This prevents users from enrolling authentication methods from unmanaged or non-compliant devices. Why this he...</summary> </entry> <entry><title>Entra device join types — Entra ID Joined, Registered, Hybrid Join (comparison)</title><link href="https://blue-sky-041ab6803.azurestaticapps.net/posts/Azure-Device-registration-Dif/" rel="alternate" type="text/html" title="Entra device join types — Entra ID Joined, Registered, Hybrid Join (comparison)" /><published>2026-01-10T07:00:00+01:00</published> <updated>2026-03-16T21:46:26+01:00</updated> <id>https://blue-sky-041ab6803.azurestaticapps.net/posts/Azure-Device-registration-Dif/</id> <content src="https://blue-sky-041ab6803.azurestaticapps.net/posts/Azure-Device-registration-Dif/" /> <author> <name>gudszent</name> </author> <category term="Azure" /> <category term="Identity" /> <category term="Devices" /> <summary>I always have to start with a quick recap when discussing Entra device join types with colleagues or customers, so I decided to write it down as a blog post for future reference. This article compares the three common Entra device states: Entra ID Joined, Entra ID Registered (workplace-registered), and Hybrid Entra Join. It explains when to use each, requirements, licensing considerations and ...</summary> </entry> </feed>
