SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It sounds like the best practice for isolating different customers on an extranet is to use separate site collections for each customer (as is recommended in every answer to this question). If I have UAG available, I'm wondering if it would be a suitable replacement. I have two questions regarding this:

  1. Could UAG provide the same level of isolation without the added complexity of maintaining over 200 site collections?
  2. What drawbacks might this have (e.g. not being able to turn on/off services on a per-customer basis)?
share|improve this question
up vote 3 down vote accepted

UAG is not going to "re-architect" the way SharePoint works. UAG will provide you with an added level for Defense in Depth, by forcing authentication prior to hitting SharePoint, as well as allowing you to NOT have your SharePoint servers directly to the internet via reverse proxy. You still need to define your security boundaries inside SharePoint per Site Collections, Web Apps, or even Farms.

Depending on your separation requirements, if information leakage is not a critical factor you can utilize sub-sties and audiences and just take advantage of the native security trimming. If you want separate security context's you are back to the three methods above.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.