Showing posts from 2018

Join a Microsoft Team with a Code

Join Teams with CODE
Create team first, then got to Teams settings
Joining a @MicrosoftTeams with #CODE...

1. Create a Teams 2. goto Teams Settings 3. Generate Code

Now you are ready and can set the Join Team Code to your Members

Restrict Groups Creation in Office 365

Restrict Groups Creation in Office 365

How to disable the ability to create groups in all Office 365 services that use groups:
·Microsoft Teams:
Both admins and users won't be able to create teams
Both admins and managers won't be able to create teams
Users won't be able to create a new plan in Planner web and mobile apps
The best way to do this is to create a security group, and then only the people in that security group will be able to create Office 365 Groups and teams in these apps.

You should verify your impact to Microsoft Teams. The creation of Teams, which go along with a Groups365 creation might impact the work efficiency of your users.

Groups can have a
n "end date", where the group will automatically be deleted.

However, restricting group creation will not prevent the listed members from creating Office 365 Groups from the apps and it prevents other users from creating teams (because you can…

Installing Skype for Business on Windows Server 2016 On-Premise (Version Error Solution)

If you encounter an installation error stating the wrong version is installed during the pre-requisite checks:

Follow this Registry-Setting:

Remote Login to Microsoft Teams

With Teams you can login in the same way as with SfBO, additionally, Teams Remote PowerShell Login als provides a GUI Login window.

Don't forget to install the AzureADConnect:

Beside of Msol you must NOT use the $credential variable. Instead let the connect open the Login Frame

First install the Microsoft Teams PowerShell Module:

Install-Module MicrosoftTeams

With GUI Login:


Set-ExecutionPolicy RemoteSigned
$credential = Get-Credential
Connect-MsolService -Credential $credential

Microsoft Teams
Connect-MicrosoftTeams -Credential $credential

Deplyoing Teams with MSI

It is possible for standardizeddeployments rolling out Teams with Group Policies, or Software Deployment Tools like SCCM, Martix42 or others.

The package must include:

·.NET framework 4.5 or later
Download the MSI installer:

Microsoft Teams (32bit)
Microsoft Teams (64bit)

Do not change the default installation path. This might prevent Teams from further updates.

Microsoft Teams Roadmap (implied feature list)

Here you will find the actual roadmap update be time necessary.

Microsoft Teams Direct Routing (Connect your own SBC for PSTN), including Direct Carrier Support

As in the general availability:
Microsoft Teams will support a Direct SIP connection (bring your own SIP) with SBCs on-premise.


You will require a certified SBC from Ribbon (Sonus) or AudioCodesOther SBC vendors may be added in the futureMicrosoft Teams and Phone System licences, or E5 license

Besides the primary Direct Routing scenario, we anticipate customers will want to use this capability to integrate with other 3rd party voice applications. There are several additional scenarios:

Easy Transition to Calling in Teams. By integrating with an existing PBX, pilot users can be moved to Calling in Teams while users remain on their legacy PBX. Eventually all users can be easily transitioned to Calling in Teams. The call traffic between these users during the transition stay within the organization.

Telephony System Inter/Op. While users are being transitioned to Calling in Teams, Call Center agents can continue to use their application. Direct Routing enables both use cases to c…

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.