How long do resource accounts take to properly route numbers with Direct Routing?

[Ron Prague]

I have several resource accounts created last night that all show correct (for example):

Get-CsOnlineApplicationInstance

RunspaceId : 30ab51d4-432a-4a1f-bd02-a2be5e07d65a
ObjectId : 480cb656-ff0a-4384-a4d7-980f5a3f68d6
TenantId : 341ac572-066c-46f6-bf06-b2d0c7ddf1be
UserPrincipalName : biampaa@biamp.com
ApplicationId : ce933385-9390-45d1-9512-c8d228074e07
DisplayName : Biamp Auto Attendant
PhoneNumber : tel:+15036417287

But when I try to call it via Direct Routing, I'm receiving a 404 Not Found error back from Microsoft.

Is this just yet another weird issue where you just have to sit on your thumbs and wait for Microsoft to do whatever they're doing in the back end?

I also can't call any of these resource accounts or call queues from within Teams.  They show up when you search for them, but hang up immediately.

[#2]

This is maddening.

40 hours later, still the same results.

Support is completely and 100% useless.  They don't even know what direct routing is.

I don't understand how Teams can be an enterprise platform when things happen in weird 24+ hour windows all the time.

[#3]

@Ron Prague

How did you had to wait for it to start working? I am on 26 hours. Still getting 404 unallocated number. However, everything is showing up. 

Get-CsOnlineTelephoneNumber -TelephoneNumber "mydid" 

shows no number found with given criteria. 

[#4]

@ijaved 

It took us 3 days to get it working. Added Friday 5pm and it was not active till Monday 8am. 

Get-CsOnlineTelephoneNumber -TelephoneNumber "mydid" does not show anything even when everything is working. So that's false positive.