Azure – Difference between Azure tenant and directory

azuredirectory

Are Azure "tenant" and "directory" different things, or different names for the same thing?

According to the documentation, a tenant is a container within Azure associated with a company or group of people, and a directory is a container; all directories are mutually exclusive, i.e. what you do in one directory does not affect any other.

So is there any difference or are they the same thing?

I look forward to some clarification.

Thanks in advance!

Best Answer

Overview:

An Azure Tenant is a separation boundary between one customer and another.
A Directory is an identity service that exists in a tennant.
You can have only one directory in a tenant at a time.
https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-whatis#terminology Look at the Azure AD directory entry in the terminology table.

How to create a new directory and tenant:

To create a new directory in your tennant, go to "Create a resource" -> "Azure Active Directory".
Next fill out the form to create the new directory and press the create button.
This will create a new directory and a new tenant.
Switch to the new directory by using the switch directory link in the directory switcher:

Term Clarification:

Multi-Tenant: A resource configuration where resources can access multiple tenants. E.g. users can exist in multiple tenants
Single tenant: A resource configuration where the operation is isolated to the current tenant and has no external dependencies.
Customer: A customer is a single entity that pays for one or more subscriptions/Enterprise Agreements. They can control more than one tenant/directory. E.G. Contoso Ltd., Fabrikam, Inc., WingDing Toys, etc.

Related Solutions

Ssl – Does Azure support UCC/SAN SSL Certificates

Azure supports UCC/SAN SSL certificate. But as per your image, you have tried to purchase this type ssl certificate through Azure 'App Service Certificate' that's why you were unable to find UCC/SAN certificate option from it. So purchase it from trusted SSL provider.

If your all 15 domains are first level sub domains of the main domain then you can also secure them with wildcard ssl certificate. But if they are multi domains like abc.com, app.abc.net, login.xyz.biz, signup.abc.org then SAN SSL is the best option to go for.

As per your requirements:

If you got decent amount of revenue from older browsers Windows XP/IE then don't go for SNI. But SNI doesn't fully ignore IE web browser but some of its versions. Read more on SNI supports which browser and server.

As per your questions:

Go for UCC/SAN SSL certificate to which Microsoft Azure supports.
If not want to use SNI then take different IP address for each domain which is also valid but in the 'SSL Bindings' option, you have to select SSL type as 'IP based SSL'.

Azure RecoveryServiceVault can’t be removed

Finally was able to remove the vault, after clearing the sql backups from it through powershell. I'm really surprised NO ONE knew about this and it took so much digging to find it.

commands for anyone else having this problem:

These commands are to first see if anything is in the database backups, then remove it all.

$vault = Get-AzureRmRecoveryServicesVault -Name "VaultName"

Set-AzureRmRecoveryServicesVaultContext -Vault $vault

VIEW THE BACKUP ITEMS

$container = Get-AzureRmRecoveryServicesBackupContainer -ContainerType AzureSQL -FriendlyName $vault.Name

$item = Get-AzureRmRecoveryServicesBackupItem -Container $container -WorkloadType AzureSQLDatabase

$availableBackups = Get-AzureRmRecoveryServicesBackupRecoveryPoint -Item $item

$availableBackups

REMOVE THE BACKUP ITEMS AND VAULT

$containers = Get-AzureRmRecoveryServicesBackupContainer -ContainerType AzureSQL -FriendlyName $vault.Name

ForEach ($container in $containers)
{
    $items = Get-AzureRmRecoveryServicesBackupItem -container $container -WorkloadType AzureSQLDatabase

    ForEach ($item in $items)
    {
        Disable-AzureRmRecoveryServicesBackupProtection -item $item -RemoveRecoveryPoints -ea SilentlyContinue
    }

    Unregister-AzureRmRecoveryServicesBackupContainer -Container $container
}

Remove-AzureRmRecoveryServicesVault -Vault $vault

I hope I helped some other people out there who ran into this mess.