and Set-CSUser can’t be used to allocate phone numbers either. I’d been allocating numbers with the Set-CsOnlineVoiceUser command. The replacement for this is:
Set-CsPhoneNumberAssignment and Remove-CsPhoneNumberAssignment
They run under the MicrosoftTeams module for PowerShell, but you also need to make sure you have the latest version. If you don’t have a version that supports this new command, you’ll get the error:
Set-CsPhoneNumberAssignment : The term 'Set-CsPhoneNumberAssignment' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1
To update, run the command:
Update-module MicrosoftTeams
Then try the above cmdlet again. If you’re feeling really brave, you can update all your modules with:
Update-module *
Disconnect or restart PowerShell or you’ll get problems running the new cmdlet if you had it connected while updating.
The new cmdlet Set-CsPhoneNumberAssignment doesn’t work exactly the same way as the old cmdlets. Read the documentation for more details
I thought I’d document a few lessons learned in this migration. The migration was from Skype for Business Server 2015 and Skype for Business 2016 clients with Enterprise Voice, moving users across to Microsoft Teams.
The steps to migrate a user for me were:
Add user to AD Group “Azure AD Licensing Telstra Calling for Office 365” as this allocates a Telstra Calling for Office 365 license. These licenses are bought from https://marketplace.telstra.com/ and feed into Microsoft 365. I believe this is unique to Australia.
Form a machine with the Teams PowerShell Module installed: $Session = New-CSOnlineSession -OverrideAdminDomain yourdomain.onmicrosoft.com Import-PSSession $session –AllowClobber Set-CsOnlineVoiceUser -Identity [email protected] -TelephoneNumber 61812341234 Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity [email protected]
Configure call forwarding in Gateway (Pilot Users only that were being given a new number out of our normal number range)
EHR Error on Teams Portal
We can’t get details of EHR usage. Please try again. If you continue to have problems, contact Microsoft customer support.
Seeing this error everywhere on the Teams Admin portal, unsure what the cause/fix is yet. It ended up disappearing by itself after a few weeks *shrug* – you’ll see this theme is common around portal errors.
Dial Plans error
We can’t get the effective dial plan so the dial plan can’t be tested.
Going into any Dial Plan brings up this admin portal error, as well as trying to run a Test Dial plan test:
Something went wrong while testing this phone number. If you continue to have problems, contact Microsoft customer support.
This problem was another portal issue – logged a case which Microsoft confirmed was at their end, and a few weeks later they’d resolved it.
Create Resource Account error
We can’t save changes to ___
When creating a Resource Account used for Auto Attendant or Call queues, I was getting a very unhelpful error. I believe this is because I’m running in hybrid mode, so Teams can’t create an account on my primary domain – changing the domain to @contoso.onmicrosoft.com then let me create the Resource Account.
This problem also disappeared later and now I can create accounts on my primary domain – put it down to another portal issue.
DeskPhones requiring PIN
Phones would be registered in Intune, because they’re running Android – and that means any ‘all user’ Android policy would apply.
I’ve since created Dynamic Device Groups and filtered by DeviceModel and DeviceOSType – only testing the Poly CCX500 at this stage, but will add more models as we get them. Also filtering by OStype which is not really necessary, but does make sure it’s only Android devices affected.
(device.deviceModel -eq "CCX500") and (device.deviceOSType -eq "Android")
If you use a test account 20 times, that account will hit its device limit in azure and get locked out.
Skype for Business users unable to call Teams users
Early in migration, we tested interoperability between the two platforms, as it wasn’t going to be an overnight company wide migration. A Skype for Business user trying to call a migrated to Teams user would instead get diverted elsewhere. This was because we had Unassigned Number range rules in place, that were designed to send calls somewhere if it wasn’t allocated to anyone. Removing these rules immediately fixed this issue.
Home Screen on Desk Phones Laggy
The default experience if the phone supports it, is to show a home screen. More details on what the Home Screen is here. This is in CsTeamsIPPhonePolicy with the default value ‘AllowHomeScreen’ set to ‘EnabledUserOverride’. Changing this to Disabled via the PowerShell command:
removed this. I like the idea of the Home Screen, but not at the cost of a fast functioning phone vs a slow one.
I later found out this is due to the 1GB RAM on some devices, and Teams now (at the time of writing) uses > 1GB RAM, and then the Home Screen uses even more RAM. Trying a phone model with 2GB RAM this all worked perfectly.
I believe this is also fixed now, but it took Microsoft about 5 months to resolve.
New Desk Phones not signing in
Testing the Poly CCX500 model, some wouldn’t sign in to Teams out of the box. As soon as I tried to sign in, they’d say:
‘Error Could not sign in. You will need to sign in again. If you see this message again, please contact your company support. OK’
I spent so long on this, unsuccessfully trying to update the firmware via USB etc. In the end, turning off the ‘DHCP Time’ setting under ‘Device Settings’ made it work – I assume it had some problems contacting a NTP server (settings appeared correct in the DHCP scope of the phone). Someone else found the same issue here, but this was due to the phone running a very old v1 firmware. This shouldn’t affect most people, but worth noting.
Disconnect the power, then power on the Poly phone.
As soon as the Poly logo shows on the screen, press and hold the four corners of the LCD display. Note: It may take several tries to get the timing right or to find the correct spots to press on the LCD display.
Release the LCD display when the Mute indicator on the lower-right corner of the phone begins flashing red, amber, and green.
However, I tried this many times without success. Doing large crab claw fingers to cover the 4 corners of the screen was doing nothing beyond hurting my fingers.
I ended up working out it was a timing thing, and the Poly logo shows twice. It will first show, then go to a black screen for a second or two, then re-show the Poly logo. If you press the 4 corners before the Poly logo comes up for the second time – nothing happens. You have to press the 4 corners of the touch screen straight away AFTER the Poly logo has come up for the second time. It won’t register if you do it earlier, and leave your fingers in the right place.
They actually have a video showing this correctly:
Hope this saves someone time! I assume this is the same for CCX 400, CCX 600, Poly Trio C60 etc but haven’t tested those.
Note the default admin password for these phones is ‘456’ and you should be changing this, which is easily done automatically via a Teams Configuration Profile
Microsoft Lists is available for a lot of people already, and should be globally available by the end of October 2020. Users can start using it as soon as it’s released for your tenant, which is great; but you might get caught out by the same date and time regional problem I did.
Creating a List is easy (right now I have the option available in Teams, but the app in Office 365 hasn’t turned up yet), and there’s many use cases for wanting a date or time field.
However, the suggestion on what day it is was wrong:
Today is actually Wednesday, October 14th 2020. It’s being caused because the timezone is wrong for the list. How do we fix that?
A Microsoft List can be created two ways – in the single user context, or in a Microsoft 365 Group context. If you’re doing in in Teams then the later only applies. Individually, it’s saved in the same area as your OneDrive for Business (which is backeneded by SharePoint), but for a Group it’s saved straight into the Site for the Group.
Lists in OneDrive for Business
For the individual point of view, there’s already a Microsoft Answer on how to fix this – change your Time Zone and Region Locale. The link for this is indivualised for your tenant and account, but you can access it by:
Click the cog in the top right corner and choose ‘OneDrive Settings’
Click ‘More Settings’ in the left hand list
Under ‘Region and Language’ choose ‘Regional Settings’
Choose the correct Time Zone and Locale for your account
Changing this for all users is a bit more of a problem. There’s a PowerShell script here to update all existing ones, and new users there appears to be no way to do it based on this outstanding UserVoice – if you find anything different, please share and I’ll update this post.
Lists in SharePoint Online
A Microsoft List tied to a Microsoft 365 Group will read the Time Zone and Region settings from the Group’s site, which is accessed a bit differently:
If you have the Lists app in the left hand menu, choose that and skip to step 5
If there is no Lists app, click the SharePoint app from the left hand menu
Choose the Microsoft 365 Group that contains the Microsoft List (if you’re unsure, you can try finding the List in Teams, clicking the elipsis and choosing ‘Open in SharePoint’.
Click the cog in the top right corner and choose ‘Site Contents’ then choose ‘Site Settings’
Click ‘Regional Settings’ under ‘Site Administration’
Choose the correct Time Zone and Locale for your Group and press ‘OK’ in the bottom right corner.
This works for a single site, but what about a company wide default?
In the SharePoint admin center, under Settings then Site creation, you can set the default time zone for new sites. This won’t help any existing Microsoft 365 Group already created (as a site is created at the time the group gets created), but will help with future sites.
If you want to update existing sites in PowerShell, you’ll need to start with this command:
A lot of details there just to change the date detection in Lists, but hopefully this gives you enough information to understand the scenarios and how to resolve them.
When Cloud Voicemail a.k.a. Azure Voicemail (which replaced Unified Messaging) is activated for a mailbox, a default language is set. This value is known as the ‘promptlanguage’ and according to Microsoft Documentation will be set based on the default language for your organisation in the Microsoft 365 admin center.
The problem is, that value is ‘English’ and doesn’t define which regional set of English you want – en-US, en-UK, en-AU etc. The full list of language codes is available here.
With Engish set as the preferred language, Azure Voicemail decides that you must be wanting en-US as your promptlanguage – which you may not actually want. The default voicemail greeting is rather different when set to en-US vs en-UK vs en-AU.
If you’d like to see what a user has, use the PowerShell command:
On a per user basis, this value can be changed either by the user themselves at https://mysettings.lync.com/voicemail or by an admin with the PowerShell command:
This still doesn’t solve the tenant wide problem, or set a default.
For existing users, we just need to get a list of users and change the promptlanguage setting, which can be done with this set of PowerShell commands (includes connecting to SfBO which can be used for the above command also):
foreach ($user in $users) {set-csonlinevoicemailusersettings -identity $user.userprincipalname -promptlanguage en-AU}
Note the use of the -OverrideAdminDomain switch, which I learnt from this blog post in case you are having issues connecting to Skype for Business Online.
This process also may take a long time depending how many users you have, as very roughly it takes about a second per user to change the value.
This will fix your existing users, but what about new ones? You could have the setting modified set as part of the user creation process, but that’s an extra step and you’d need to wait for Azure Voicemail to be ready – in my experience it’s not a service that’ll be available quickly after enabling. At this stage I haven’t found a way to do it though, so you’ll need to consider adding this configuration as part of user setup.
If you haven’t even thought about what language you’re using – have a look and try each one, as you might find one that you’re happier with than the US.
