Posts

Restrict Groups Creation in Office 365

Image
Restrict Groups Creation in Office 365


How to disable the ability to create groups in all Office 365 services that use groups:
·Outlook
·SharePoint
·Yammer
·Microsoft Teams:
Both admins and users won't be able to create teams
·StaffHub
Both admins and managers won't be able to create teams
·Planner
Users won't be able to create a new plan in Planner web and mobile apps
·PowerBI
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.



NOTE:
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.

N
ote:
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)

Image
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

Image
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:
https://www.microsoft.com/en-us/download/details.aspx?id=47594


NOTE - MULTI-FACTOR AUTHENICATION:
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:
Connect-MicrosoftTeams





MicrosoftOnlineLogin

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)

IMPORTANT:
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.

https://aka.ms/skype2teamsroadmap

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

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



Requirements:


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…