01-06-2022 10:43 AM
On initial load of advanced insights (i.e. going to https://workplaceanalytics.office.com/) as per Viva Insights setup | Microsoft Docs .... we wait for it to "do its thing" and then get to the provisioning page as per below. We happened to execute this in two tenants yesterday, more or less in parallel. In one tenant, the provisioning was minutes (not sure how long, but let's say well under 30 min). In the other tenant, we are still waiting. Screenshot below is after +24h. Obviously have tried to clear various caches, login with another insights admin account, etc.
Has anyone else experienced a delay like this? What did you do to resolve it? Just wait, or did you need someone from support to go kick a virtual rack in the cloud?
Thanks for sharing any tips or shared pains.
Gabriel
Solved! Go to Solution.
02-09-2022 08:01 AM
Hi Jake - I am happy to let you know that today after +3 weeks, the issue appears to be resolved. The ticket was - after some false starts - finally escalated to the engineering team as you know. Since then it took about 2 weeks to resolve. I still don't know what the issue was - but I hope to get some detail.
I think now we can finally mark this thread as solution provided 😉
01-07-2022 08:58 AM
Hi @Gabriel, did you provision the licenses then immediately upload HR data and confirm admin settings? If so, it may take ~3 days for the system to get up and running. Sometimes the set up is pretty quick as you noticed with one tenant but other times it can take up to ~3 days. I would advise you to check back later today or on Monday to see if the set up has completed.
01-08-2022 01:13 AM
Thanks Jake.
Licenses where added 30 or 31 Dec. We only jumped into the workplaceanalytics.office.com URL on Wed (now about 60 hours ago).
HR/Organisational data has not been added yet, as we are still waiting for the provisioning to complete. It's still stuck on the provisioning screen (as per screenshot in the original post). I will check in again next couple of days.
Thanks
Gabriel
01-09-2022 02:55 AM
And still waiting (+72 hours now). One thought..... this tenant is a non-production tenant, and therefore has very low user activity. There will be very little Teams chat or emailing activity - and whatever there is, will be between only a handful of users (as it is a non-production environment for demonstration purposes mainly). Does the provisioning require a certain threshold of historic activity before it can "do its thing" and complete?
01-10-2022 01:12 PM
And still waiting @Jake_Caddes, so now it would be 5 full days. As per my last reply, would be good to know if we should expect this ever to work in a low-activity non-prod environment. Do you prefer I raise it as a proper support ticket?
01-12-2022 08:45 AM
Hi @Gabriel, yes I would suggest you to raise a support ticket. Typically, it would take about 3 days for a tenant to get set up after the licenses have been assigned and the admin settings have been confirmed. Since it is taking much longer than that I agree a support ticket would be the best path forward to solving this issue. I'd mention in your ticket that you need to turn on this tenant since it is a brand new tenant but it has stalled somewhere during the processing/set up stage.
01-21-2022 01:08 AM
Hi there. Just FYI - I am having an incredibly poor support experience. I will be feeding this back to the JumpStart team as well.
(btw - this thread is mark as having an accepted solution,.... it really doesn't)
01-21-2022 09:53 AM
Hi @Gabriel, I am so sorry to hear that the ticketing process has gone so poorly for you. Can you please DM me your tenant information and ticket number for the issue and I will try to escalate the ticket via engineering to look into your tenant and try to expedite the fix?
01-21-2022 10:27 AM
Thanks Jake - done 😉
02-09-2022 08:01 AM
Hi Jake - I am happy to let you know that today after +3 weeks, the issue appears to be resolved. The ticket was - after some false starts - finally escalated to the engineering team as you know. Since then it took about 2 weeks to resolve. I still don't know what the issue was - but I hope to get some detail.
I think now we can finally mark this thread as solution provided 😉