Very nicely described and the documentation looks so complete. Can't wait to read through and explore..! Thanks for putting all this information together! :)
Thank you so much for the informative video. Multitenancy, in general, is a bit challenging, especially when it comes to managing tenants and their subscriptions through a dedicated tenant administration portal. This is in conjunction with data isolation strategies such as a Shared Database for All Tenants and a Separate Database Per Tenant. We dedicated the past four years to analyzing and studying the best practices that should be considered when building a SaaS app using the Multitenancy approach.
The multitenancy guidance is more about how you design individual applications or workloads, while CAF and landing zones are about managing your whole Azure estate. However, we've also published some information that might be helpful: docs.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/isv-landing-zone
Hi David, to get the best advice on this, we recommend reaching out to our Azure Community here: msft.it/6052jEdQw The community is a great place to get help, advice and guidance for Azure users.
Extreme high level approach :( Things you showed are just isolating tenants on resources and not really using the Cloud like PaaS. Things you showed can be easily done in a Kubernetes Cluster. More interesting would be Scaling for example in CosmosDB or how to integrate Azure B2C or API Management and split Storage and Compute clear ... and so on..
Please check out the guidance at aka.ms/multitenancy - it includes some of these points already (e.g. how to split up storage accounts and Cosmos DB accounts), and we are working on guidance around Azure AD and AKS at the moment :)
@@johndnz Hey John, thanks for your reply. I see there are some examples. Still this multi tenant approach is more on a fixed tenant wise application. Solutions which can fit infinite Tenants will use different approaches. Either way, I guess in the end every project is specific and needs planning. In our usecase for example we learned that front door is way too expensive and also can't handle A Records, I would only use it for certain applications, just to name a example.
Very nicely described and the documentation looks so complete. Can't wait to read through and explore..!
Thanks for putting all this information together! :)
Thanks for the beautiful session
Awesome, thanks for the video
Awesome as always
Thank you for the great sharing
Please do more of these videos!
I will Thanks
Thank you so much for the informative video. Multitenancy, in general, is a bit challenging, especially when it comes to managing tenants and their subscriptions through a dedicated tenant administration portal. This is in conjunction with data isolation strategies such as a Shared Database for All Tenants and a Separate Database Per Tenant. We dedicated the past four years to analyzing and studying the best practices that should be considered when building a SaaS app using the Multitenancy approach.
GREAT session guys thanks a lo t...
Thank you
I wish this was a playlist on your channel.
Excellent!
This subject matter *should* be its own role-based or specialty certification for Azure...
Does SOC 2 compliance require a certain model?
How does this fit with CAF and Enterprise Landing Zones?
The multitenancy guidance is more about how you design individual applications or workloads, while CAF and landing zones are about managing your whole Azure estate. However, we've also published some information that might be helpful: docs.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/isv-landing-zone
nice
Any nugget packages you would recommend for multi-tenant?
Hi David, to get the best advice on this, we recommend reaching out to our Azure Community here: msft.it/6052jEdQw
The community is a great place to get help, advice and guidance for Azure users.
Extreme high level approach :( Things you showed are just isolating tenants on resources and not really using the Cloud like PaaS. Things you showed can be easily done in a Kubernetes Cluster. More interesting would be Scaling for example in CosmosDB or how to integrate Azure B2C or API Management and split Storage and Compute clear ... and so on..
Please check out the guidance at aka.ms/multitenancy - it includes some of these points already (e.g. how to split up storage accounts and Cosmos DB accounts), and we are working on guidance around Azure AD and AKS at the moment :)
@@johndnz Hey John, thanks for your reply. I see there are some examples. Still this multi tenant approach is more on a fixed tenant wise application. Solutions which can fit infinite Tenants will use different approaches. Either way, I guess in the end every project is specific and needs planning. In our usecase for example we learned that front door is way too expensive and also can't handle A Records, I would only use it for certain applications, just to name a example.
FRANCA SP BRASIL .
thi sis a useless session just should have shared links in ONE SLIDE.. Waste of TIME!