I understood the following from this lecture, correct me if I am wrong. A company signs up for an Enrollment with Microsoft. Then it Creates a Tenant and within the Enrollment, within the Tenant it creates different Subscriptions for different divisions within that company to manage the bills for each divisions separately. Or it can create different tenants for different branches if they are located in different cities and then within each branch they can have multiple Subscriptions depending on how many different departments each branch has, to properly manage the billings
Thank you for this. Many Azure clients use the concepts of "Subscriptions" to encapsulate an "environment", eg. DEV, QA, PROD. Would you see any issue using one Tenant that contains all prod and non-prod subscriptions (environments)?
I've seen this 'think of a tenant as an apartment' attempt to explain it. So then what is the person who lives in the apartment called, also a tenant?? >_> That's the worst example they could've come up with to explain this concept.
I don't think I understand any better after watching the video. When I create a tenant, "inside" of what is it being created? I notice that inside my Azure portal, I have the ability to create tenants, publishers and subscriptions. What is my Azure portal? Is it a tenant or a subscription? If a subscription, then that means that subscriptions can contain subscriptions? And if a tenant, then tenants can contain tenants? What is the point of all this (recursive?) hierarchy?
I've gotta ask... what's up with the opener with the drone for 30 seconds with no sound? 😅
Very nice explanation and illustrations. Thanks for all of it!
Well explained, I am a non-technical person as working; however got the point in first go.
Thanks!
I understood the following from this lecture, correct me if I am wrong. A company signs up for an Enrollment with Microsoft. Then it Creates a Tenant and within the Enrollment, within the Tenant it creates different Subscriptions for different divisions within that company to manage the bills for each divisions separately. Or it can create different tenants for different branches if they are located in different cities and then within each branch they can have multiple Subscriptions depending on how many different departments each branch has, to properly manage the billings
So helpful! Thanks so much ❤️
Nice Explanation of concepts ... Many Thanks !
The mud is still murky.
VERY MURKY!
helpful! Thanks so much
Best part was explanation of tenant.
Azure AD resides in the subscription?
Very very confusing after 6:32.
Still valid in 2021 super 👌
What does O365 Data centre mean? I was under the impression that a Data Centre can have both Office 365 and Dynamics 365?
why is there a drone on the film???
Thank you for this. Many Azure clients use the concepts of "Subscriptions" to encapsulate an "environment", eg. DEV, QA, PROD. Would you see any issue using one Tenant that contains all prod and non-prod subscriptions (environments)?
Better approach is to use resource groups. RGs are more suited for ALM and SUBS are suited for billing and transactions.
I've seen this 'think of a tenant as an apartment' attempt to explain it. So then what is the person who lives in the apartment called, also a tenant?? >_> That's the worst example they could've come up with to explain this concept.
I don't think I understand any better after watching the video. When I create a tenant, "inside" of what is it being created? I notice that inside my Azure portal, I have the ability to create tenants, publishers and subscriptions. What is my Azure portal? Is it a tenant or a subscription? If a subscription, then that means that subscriptions can contain subscriptions? And if a tenant, then tenants can contain tenants? What is the point of all this (recursive?) hierarchy?
It’s because this is Microsoft. They do everything complex
a simple DIAGRAM would have been much better .... disliked