harbar.net component based software & platform hygiene

Rational Guide to Multi Tenancy with SharePoint 2010, Part Six: Provisioning Tenants

Print | posted on Tuesday, September 14, 2010 1:22 PM

This, the sixth part of the Rational Guide article on multi tenancy, will walk through the creation of feature packs and the provisioning of Tenants for the sample scenario detailed in part three.

Provisioning Tenants

If you haven’t checked out the previous parts, I strongly encourage you to review them. I won’t repeat information and I assume you have read the previous parts, which are:

  1. Feature and Capability Overview
  2. Planning your Deployment
  3. Example Scenario and what Multi Tenancy brings to the party
  4. Configuring the base Infrastructure
  5. Creating Partitioned Service Applications
  6. Provisioning Tenants (this article)
  7. Testing the Functionality and other considerations

IMPORTANT: You must have run the scripts in the order presented in this series. If you haven’t run the scripts in part four, you should go do that before proceeding!

So far in the article series we have configured the core infrastructure and created service applications in partitioned mode. Whilst there are a few nuances to those steps which are critical to success, there is nothing clever going on so far, and we have zero functionality. Now we look at the really interesting part of the deployment, actually provisioning tenants and setting up the service applications to work with them.

Provisioning Tenants

.

Feedback

Gravatar

# re: Rational Guide to Multi Tenancy with SharePoint 2010, Part Six: Provisioning Tenants

First of all great series I have learned a lot from it. I do a have question in regards to multi-tenacy and an enterprise environment vs a hosted environment. If one were to use multi-tenancy in an enterprise environment, to consolidate multiple farms into one farm for the enterprise, where the users accounts weren't in seperate OU's would that be possible. And if it is possible how would that affect the user profile service, could all the tenants share the same My Site URL, say my.company.com rather than tenant.company.com/my in a partitoned service app.

9/22/2010 6:58 PM | Jeremy Weiss
Gravatar

# re: Rational Guide to Multi Tenancy with SharePoint 2010, Part Six: Provisioning Tenants

Hi Jerermy,

Whilst that model is not the intended approach to multi-tenancy, you could have the same mysite host for each of your tennts, there's no technical requirement to have a seperate host for each tenant. The issue will be the SynchronizationOU setting - this would need to be the same for each tenant and mean that you would be importing all users for each tenant (dupliction). In addiiton the people picker configuration (it would be empty) would expose all users to all subscriptions. I'd strongly urge you to look at reoganizing the domain structure if you are wanting to use the multi-tenacy capability.

9/22/2010 7:09 PM | harbars
Gravatar

# re: Rational Guide to Multi Tenancy with SharePoint 2010, Part Six: Provisioning Tenants

thanks for the clarification on this and suggestion. I was trying to figure out a way where the case may arise where one tenant may need to collaborate with another tenant without creating multiple domain accounts.

9/22/2010 10:06 PM | Jeremy Weiss

Post Comment

Title  
Name  
Email
Url
Comment   
Please add 6 and 1 and type the answer here: