carinas
Jul 03, 2019Copper Contributor
Hybrid environment and two IT providors
Not sure how to explain this issue in without writing a essay, but I will give it a try.
Customer "A" is changing their CSP partner to a new IT provider. Circumstances make it necessary to leave a part of the old environment behind. One part of the environment is on prem at the old providers data center, among other resources there is an SQL database in the on prem domain (comman domain containing several customers) and the other part, also an SQL server is in azure. The server in Azure is domain joined in the common on prem domain. The on prem SQL uploads data to the SQL in azure and there is a VPN connection. The new CSP partner is taking over the tenant and moving all users to a new hybrid environment (Azure AD Connect). There is a site2site VPN between the two providers data centers and DNS forwarding. Is it possible to ceep the old environment, meaning not touching the SQL server in Azure and leaving the full responsibility of that server to the old provider? Secondly what other issues can this (messy) environment cause? The users will need to authenticate with old providers domain users when using the services, but I can't shake the feeling that we are missing something important...
Customer "A" is changing their CSP partner to a new IT provider. Circumstances make it necessary to leave a part of the old environment behind. One part of the environment is on prem at the old providers data center, among other resources there is an SQL database in the on prem domain (comman domain containing several customers) and the other part, also an SQL server is in azure. The server in Azure is domain joined in the common on prem domain. The on prem SQL uploads data to the SQL in azure and there is a VPN connection. The new CSP partner is taking over the tenant and moving all users to a new hybrid environment (Azure AD Connect). There is a site2site VPN between the two providers data centers and DNS forwarding. Is it possible to ceep the old environment, meaning not touching the SQL server in Azure and leaving the full responsibility of that server to the old provider? Secondly what other issues can this (messy) environment cause? The users will need to authenticate with old providers domain users when using the services, but I can't shake the feeling that we are missing something important...