That is correct, although you should not see the SSID broadcasted if you have onboarded you client; the entry in the list of available networks should be replaced by the one in the profile. It may be that the old SSID still shows up just after the provisioning, but after some time only the provisioned should show up.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Feb 17, 2023 12:44 PM
From: lbrune
Subject: Aruba Central WLAN WPA2-Enterprise with Azure Cloud Authentication
Hope this can be useful.
Please do you know How I can create a different Network Profile to use WPA2-Enterprise with Microsoft Azure AD CLOUD AUTH in two different WLAN/SSIDs
At the moment from my tests I see that I can create only 1 Network Profile so I can have just 1 wlan with Microsoft Azure AD CLOUD AUTH
Is there anybody using Aruba Onboard with Microsoft Azure AD CLOUD AUTH ?
Using Microsoft Azure AD CLOUD AUTH, from my clients I see the same SSID twice (see following image), has anybody the same situation ?
In my opinion one is the ESSID in the air, and one is the ESSID form the Network profile
Thank you for any opinion