Hosting ADFS Offsite
Last Modified: 2013-12-09
Does anybody have any thoughts on deploying ADFS at an OFFSITE datacentre for Office 365 authentication?
We have recently deployed Office 365 for our 30 user organisation which is making use of federated domains and SSO.
This means we have our ADFS Main server on the primary domain controller, dirsync on another 2003 server and our ADFS proxy on another 2008 server.
These are all hosted at head office.
Currently this works wonderfully and means that users can take full advantage of SSO and they only need to remember 1 set of credentials for everything.
This works great! UNTILL our internet connection goes down at the main office and the outside world is no longer able to authenticate with ADFS servers.
This defeats the purpose entirely of hosting email services in the cloud.
The question then is: in which configuration can we still have our federated domain and SSO but NOT be reliant on a connection to head office?
One scenario I have come up with is to have a virtual server running at a local ISP datacentre, this will be a Read Only Domain Controller and be the main ADFS server.
At head office there will be the ADFS proxy.
These two locations would be connected via an already installed fiber based routed VLAN connection ( = 20Mb/s)
I am after THOUGHTS on why this will and won’t work, or if possible alternate scenarios.
I will award the best answer with the largest amount of points I can.
You would think there is a better way.
We are planning a wider Office 365 deployment and there really isn’t a way to get the ADFS servers off site. Makes no sense really if you are paying MS to hold all of our sensitive email there really is no hold back on the customer side to have a read only domain controller on the MS O365 solution. It would be a much simpler solution.
I’ve been told this is coming but as of now the guys on the ground from MS are saying ADFS onsite is still the way.
So, in our case it will be a new ADFS farm with members in two datacenters, F5 load balanced VIP for internal, F5 APM to that VIP extnerally, and then F5 GTMs in case the main datacenter side goes down and we still need that federation.domain.com to respond.
It’s a lot of infrastructure, powershell, and certificates for something that has been moved to the cloud.
The problem with not doing ADFS. Is you loose all the integration bits, the status icons in outlook, sharepoint, phones, ect. b/c you are using a domain.microsoftonline.com account vs. your internal AD account. We started that way and were missing many of the visibility and integration features. You’ll just have video and IM. And. it’s one more user/password combo to remember and compromise.
With the prevalence of social media networking tools, for retailers, reputation is critical. Have you considered the impact your network security could have in your customer’s experience? Learn more in our Retail Security Resource Kit Today!