Azure Active Directory - Tenant basics I never knew

Azure Active Directory has always been sort of just there.  I've never paid any attention to the concept of Azure Active Directory tenants until last week. Azure AD was just an idea when we first started our Azure work 8 years ago. There were all kinds of "you can't do that in Azure AD" wrappers around it back then. Azure AD has grown in flexibility. Now it is time to look at the multi-tenancy aspects of Azure AD.

You can spend years in Azure without running across the tenancy.  

  • Got a personal Azure account?  One tenant is plenty.  
  • Got an MSDN Azure subscription tied to your account? One tenant is plenty.  
  • Working in a corporate environment where some other group manages AD and provides your subscriptions?  One tenant might be all you ever use.

We can walk through an example account to get a better understanding of Azure AD tenants why we might use them.

Video

Azure AD Tenant Basics

<speaker notes to be added>

Azure AD where you are in multiple Directories / Tenants

<speaker notes to be added>



Changing Tenant in the portal
Your account exists as a user in multiple directories if you see the Switch directory link in the user profile dropdown. Click on that to see a list of Directory Tenants the user is bound to.
You will be presented with a list of directories your ID exists in.  Your permissions are immediately adjusted to the Azure AD directory that you switch to.  You operate within the scope of that directory.


What is my ID hooked to in Azure AD?
This picture shows a Microsoft ID that is bound to 4 different directories/tenants. The tenant in red is discussed in another blog article. 


Created 2022 01

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more