Please complete your April 4th To Do List before following directives for known issues. If you experience problems with your desktop app remember to use web applications on Office.com.

1. Teams desktop app authentication

Teams will automatically authenticate with your new username you@bii.co.uk. To check this has been successful click on your profile picture on the top right hand corner of your Teams desktop application.

Note: If your were not signed out before the changes your account may still read xxx@cdcgroupcom (see below).

Follow these steps for a quick fix:

Click sign out and you will be taken to the below window then select the bii.co.uk account and continue to sign in as prompted.

Click on the bii.co.uk account under 'Continue as' and sign in as prompted.

Note: If your new account is not detected in the above window, click on continue as different user and sign in with your new bii account and password.

2. Teams Web client

As changes take effect you may notice the below alerts whilst using the teams desktop app. This is due to the username changes that may impacts synchronization.

To fix this, log out and log back into Teams desktop app with you@bii.co.uk. After a successful authentication, the web app should automatically point to your new username.

Note: If you continue to see the above errors after signing in with the bii account, please wait for another 24 to 48 hrs and check again. If the issue doesn't resolve within this time period please contact Helpdesk.

3. Teams’ external communications

If you notice any communications sent to external contacts in 1-2-1 teams chats failed to send, please notify the helpdesk.

Expected behaviour : You may receive ‘Failed to send’ errors on messages and the profile for the external user may appears as ‘Unknown user'.

You will still be able to communicate to the ext user via email. This issue can only be fixed via the ext users IT department, please communicate that due to the change to BII their IT administrator will need to whitelist bii.co.uk in Teams admin centre.

4. Document sharing in Teams

The Rename changes will cause a delay on some app functionalities. You may notice the below error while sharing documents in Teams. This is an expected behaviour.

Please wait between 24-48 hrs for this issue to auto-resolve. If you continue to have issues outside this timeline, please contact helpdesk.

5. Teams meetings Webex link

Due to the rename changes, the link within Teams invites will no longer work from Webex enabled meeting rooms when using the green Join button.

Follow the steps below with full instructions found here.

Note: It has been reported that from 4 April, the first team meeting created adds a cdcgroup@m.webex.com link, whereas the following meetings created automatically input the britishinternationalinvestment@m.webex.com link. There is no workaround so please update the link for your first meeting.

Teams meetings created prior to the rename will not work using the green join button on Cisco Webex equipment.

In order for the green button to work, carry out the following. This will only work for the original organiser of the meeting.

Open the Teams meeting in the Outlook Calendar and locate the “Join with a video conferencing device” section. Right click on “Alternate VTC instructions” and select Edit Hyperlink

Where is says cdcgroup in the address, overtype with britishinternationalinvestment and then click OK. Select Send Update to update the meeting

The Teams meeting will now work using the green join button on the Cisco Webex Touch Panel.