Microsoft Teams or Skype for Business Client do not display special characters correctly

It can be happen that Teams or Skype for Business do not display the "Umlaute", special charades correctly (e.g. ö, ä, ü é,°) and so on.

This is Teams and Skype for business required UTF-8 decoding, which is the SIP Standard in any IM invite. If your encounter this problem, change your windows back to the UTF-8 encoding mechanism.

Follow the steps below to set up non-unicode language in windows 10
1. In search tab type "Region" and press enter.
2. In new window select "Administrative"
3. then click on "change system locale"
4. Select the language.

OR and try Outlook too. Else its recommended to repair or even reinstall Office.

Teams Admin Center in Office 365

The new Microsoft Teams Admin Center has arrived.

You can access as an Office 365 Admin the new Teams Admin Center:

Best for us is, that we 1st can slowly prepare for the shift from SfB to Teams. Therefore, it is not possible managing policies easily within this new Admin Portal. This portal is under constant development and will further grow over the comming month.

NOTE:When the migration of these settings is complete, we’ll disable them in the Office 365 Admin center and the Skype for Business Admin center.
Admin Center Features:Microsoft Teams messaging policy: Create policy for user-level management of the Microsoft Teams client experience for Messaging scenarios.Microsoft Teams interop policy: Configure the interoperability experience between Skype for Business and Microsoft Teams.Microsoft Teams guest messaging settings: Control the messaging capabilities for guest accounts in Microsoft Teams. Federation settings: Manage the federation betw…

Microsoft Teams MSI Installer

You can now install and distribute the Windows Teams Client via an MSI package.

Simply download the installer and run it.

Download 32bit
Download 64bit

There are prerequisites:
1. 3.32GB of disk space for each user profile (recommended)
2. Windows 7 or later.
3. NET framework 4.5 or later

Deployment Procedure (Recommendations)
1. Retrieve the latest package
2. Use the defaults prepopulated by the MSI
3. Deploy to machines when possible

For lager deployments, it is recommended using SCCM, Group Policies or Intunes.


MFA with Guest Access and different tenants settings

There is an update regarding MFA Multi Factor Authentication.

If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way.
Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow.

Login to your Profile in Office 365/ Azure AD:

Go to your PROFILE:

Sign in to
Select your account name in the top right, then select profile.
Select Additional security verification.

If might be happen, your admin hast configured MFA, so you wouldn't see this menu.
Simply switch the tenant to the guest tenant where you need to configure MFA.

Once you go back to your profile and you will find the MFA device and other settings a usual:

MFA User cannot access Mobile Phone e.g. lost phone (work around)

One-time bypass  is the solution:
The one-time bypass feature allows a user to authenticate a single time without performing two-step verification. The bypass is temporary and expires after a specified number of seconds.
In situations where the mobile app or phone is not receiving a notification or phone call, you can allow a one-time bypass so the user can access the desired resource.

Create a one-time bypass

Sign in to the Azure portal as an administrator.

Browse to Azure Active Directory > MFA Server > One-time bypass.
Select Add.
If necessary, select the replication group for the bypass.
Enter the username as
Enter the number of seconds that the bypass should last.
Enter the reason for the bypass.
Select Add.
The time limit goes into effect immediately.
The user needs to sign in before the one-time bypass expires.

View the one-time bypass reportSign in to the Azure portal.
Browse to Active Directory > MFA Server > One-time bypass.


Microsoft Phone System Voicemail with Teams

Recently Microsoft started changing their Office 365 environment utilizing more Azure based service. One of the first services moved into an Azure model was the Exchange Voicemail service. It now resides in Azure.
This service as a product is now named Microsoft Phone System Voicemail.
The works with Skype for Business and Teams in the following setups with either PSTN Calling (Microsoft cloud based PSTN) or PSTN Hybrid Voice (PSTN On-Premise)

Calling Plan Hybrid Voice (PSTN On-Prem) Skype for Business YES YES Teams YES NO

Next, we need to consider the correlation with Exchange UM and Phone System Voice Mail.
Voicemail Option with Skype for Business and Teams
Exchange UM Phone System Voicemail
Exch UM On-Premise Exch UM online User Mbx homed Exch On-Premise

Active Directory Object missing (AAD) with Teams/ Skype for Business online

This reported issue "Active Directory Object missing" is most likely happen if your run an Office 365 Tenant smaller than RING 4. Mainly TAP Tenant. 
Else if you experience those issues within your Customer Tenant, simply follow the same procedure.
It can be with any objects, which have a correlated AAD object. (AAD = Azure Active Directory)

The problem occurs, if there are any inconsistence between the AAD and CMS objects. Saving the configuration from CMS into the AAD object is what’s happening in the background and will therefore solve the issue.

First login to you Office 365 Tenant and navigate to Skype for Business Admin Center (later Communication) and locate the object having this issue...

 Next open the object and press "Edit"

Once the object configuration opens, don't change anything and click "Save"

Now the object configuration will be saved to AAD 
If a message like this "Active Directory object for location the xxx requires re-provisioning&quo…