Migrating Workspace ONE Access On-Premises to the Cloud

[Andreano Lanusse]

@Sascha Warno published this article late last year to help our customer to migrate their Workspace ONE Access on-premises instance to the Cloud, the article helps you understand what it takes to perform this migration and describes the necessary steps to plan and execute the migration.

https://techzone.omnissa.com/resource/workspace-one-access-premises-cloud-migration

[Daniel Keer]

@Andreano Lanusse

does this mean that Workspace One Access on prem is being phased out?

[Sascha Warno]

We will have the status quo for now where we (for a while already) developed new features exclusively for Access in the Cloud. To use Access with all capabilities and without the need for managing and maintaining a complex 3 node+ cluster we suggest the use of cloud Access, especially for a service that requires high availability like Access. We are aware that there are various regulatory requirements to host identities in other locations then what we offer at the moment and explore possible solutions for the longterm future. 

[Rico]

What I really miss is the ability to use our own domain name for example portal.contoso.com instead of customer.vmwareidentity.de.

Users don’t understand this URL. 

Why it is not possible to make use of CNAME records? 

Edited June 4 by Rico

[John Kramer]

Rico it is possible to use a custom URL there are three options depending on where your at in the deployment process. It would be best to configure the custom URL upfront before you have active users in the system. The vanity URL option may be the best option for you.

https://docs.omnissa.com/bundle/WS1CloudAdminHub/page/CloudAdminHubChangeAccessURL.html

[Rico]

8 hours ago, John Kramer said:

Rico it is possible to use a custom URL there are three options depending on where your at in the deployment process. It would be best to configure the custom URL upfront before you have active users in the system. The vanity URL option may be the best option for you.

https://docs.omnissa.com/bundle/WS1CloudAdminHub/page/CloudAdminHubChangeAccessURL.html

@John Kramer thank you. It looks like I still need a on-premise load balancer (for example F5 or KEMP) for just doing a 301 HTTP request. Why we can't just set a CNAME record in DNS and forward it to the IP-address of the Workspace One Cloud service?

[Sascha Warno]

The 301 redirect is your only option for a completely custom vanity URL, so just a DNS record. The rest only changes the customer part of the tenant url and with that changes the namespace internally.

[Rico]

1 hour ago, Sascha Warno said:

The 301 redirect is your only option for a completely custom vanity URL, so just a DNS record. The rest only changes the customer part of the tenant url and with that changes the namespace internally.

I understand, the only disadvantage of the 301 redirect is you still need to have a load balancer. Isn't it?

[Sascha Warno]

You are right an LB config is required, but usually an LB exist for the usually exists for the domain to be used as vanity domain.

Edited June 5 by Sascha Warno