The transition to Broadcom starts on Tuesday, April 30, 2024, at 5:00 p.m. (PDT). The timeline of changes that are scheduled to take place in VMware Cloud Services console
Timeframe |
Information |
26th April, 2024 to 4th May, 2024 |
Users with a VMware ID account will receive email from Broadcom GTO with instructions on account activation. Users should complete this before May 6th, 2024 |
30th April, 2024 |
Following features are impacted in the VMware Cloud Services console Identity
Commerce
|
4th May, 2024 to 5th May, 2024 |
VMware Cloud Services will be in maintenance mode. You will be able to perform only read operations during this time period. |
May 6th, 2024 |
User login flow will be impacted. Non-federated users using a VMware ID account should have activated their Broadcom account in order to log in to VMware Cloud Services. All the other changes in the console are summarized in this page. |
May 6th, 2024 |
Workspace One Access and Horizon customers will no longer have access to these services via VMware Cloud Services. Please utilize the latest console provided for EUC services. For further details, refer to the documentation provided here. |
May 21st, 2024 |
New Broadcom subscription data related to VMware Cloud Foundation will be shown in the UI, including Serial numbers assigned. |
Customer Support has been moved to the Broadcom Support portal. Click here to view information on customer support services.
Product licensing has been moved to the Broadcom Support portal. Click here to view information on product licensing.
Refer to this article to read about the changes in the VMware Cloud Service console.
All Customer Connect users will be migrated to Broadcom accounts. Customers will receive an email from Broadcom GTO requesting them to activate their accounts, create a new password and set up MFA, if relevant. Emails from Broadcom will be sent between April 26 - May 6, on a rolling basis. Post May 6 (referred to as Day 2), customers will be asked to login with their new Broadcom account credentials, and Customer Connect accounts will become inactive.
Currently, two different types of accounts are used to access the VMware Cloud Console: VMware Customer Connect (VMware ID), and federated accounts (i.e., corporate credentials).
If you are using VMware ID to log in:
If you are using federated account to perform Single Sign On:
The impact on May 6th is primarily for customers who were using Customer Connect credentials (VMware ID) to log in to VMware Cloud Console. These users will have to follow the instructions sent out by Broadcom before May 6th in order to log in to Cloud Console post Day 2.
Even if you are a federated customer, i.e., you use corporate credentials to log in to VMware Cloud Console, there will be at least 1 user in your organization who has a Customer Connect account. The user would have used this account to raise support requests, download binaries, purchase subscriptions in Customer Connect. These users WILL receive the account activation email from Broadcom, and MUST follow the instructions in order to access the Broadcom Support Portal.
On a long term basis, federated customers will also be asked to perform certain migration procedures in order to point your Identity Provider to the latest systems. However, this is scheduled to take place in a phased manner, starting May 1st, 2024. No immediate action is required.
Refer to this KB to understand the list of steps you need to follow to activate your Broadcom Account.
The emails from Broadcom are being sent out in phases starting April 29th, 2024. If you haven’t received an email even after May 4th, 2024, it could be because of one of the following reasons:
If you were using an active VMware ID account, and still haven’t received the email, reach out to Broadcom Support for assistance.
Continue using your old password to log in to VMware Cloud Services until May 4th. Between May 4th and May 5th, the VMware Cloud Services console will be in read-only mode. Starting May 6th onwards, please use the new password that you created during Broadcom account activation.
If you are using VMware ID to log in, please ensure you have completed all the steps as instructed in the email sent out by Broadcom.
If you have completed all the steps successfully, and, yet you are unable to log in, reach out to Broadcom Support for assistance.
If you are a federated customer, the MFA you use in VMware Cloud Services depends on your Identity Provider. You are not impacted by this change.
If you are a VMware ID user, and you had enabled organization level MFA mandate in CSP Authentication Policy, you WILL be impacted.
After April 30, MFA functionality for customers using Customer Connect to log in will change, and organization-level policy will be removed from the CSP portal, after which, multi-factor authentication configuration or modification will be disabled. You cannot perform new MFA configurations or modifications to existing MFA configurations in CSP.
After May 6, all MFA functionality will rely on the Broadcom account MFA support.
Federated accounts using MFA as part of their IdP’s authentication process will NOT be affected by these changes to VMware Customer Connect accounts.
Users who are part of the Broadcom site, i.e., enterprise users will be prompted for MFA enrollment as part of the Broadcom account activation process. If you wish to mandate MFA enrollment for any user, then follow the instructions in this KB article to add a user to your Broadcom Site.
Broadcom Okta IdP supports multiple authentication methods. Customers must set up at least one of them to enable MFA. The following authentication methods are supported:
Broadcom MFA validation will only be prompted when there’s an identified change in log in behavior (location, device, IP address, etc.). Therefore, users might not be required to enter MFA verification at every login.
Please refer to the Broadcom Knowledge base article User Registration Multi-Factor Authentication Setup Instructions to learn how to set up MFA.
You will not be able to view usage data for non-VMware Cloud Foundation services in VMware Cloud Services. For services within the VMware Cloud Foundation product family, you will be able to view consumption usage data and historical data.Overage data will not immediately be available while we transition across data services. While our backend data services are being migrated, stale or outdated usage data might be displayed. You will see a banner in the VMware Cloud Services console stating some of the data is stale or outdated while we work through these migrations.
If you need immediate access to usage data that is currently not displayed in the VMware Cloud Services Usage Management interface, please contact Broadcom Support for assistance.
The VMware Cloud Services portal will no longer support Payment Method management as this will be handled by Broadcom IT systems and migrated to Broadcom. For any new customers, payment methods will be set up as part of the sales process. Please see here for more information on how to pay.
All subscription management will be available and managed through the Broadcom infrastructure, however you will be able to view read-only subscription data in relation to any services that are a part of the VMware Cloud Foundation product family within the VMware Cloud Services console.
You will not be able to create, amend, renew, cancel or take any action on subscriptions within the VMware Cloud Services console.
No, the Promotional Credits feature is deprecated and is no longer available within the VMware Cloud Services console.