Microsoft Teams ist der zentrale Ort für die sichere und produktive Zusammenarbeit in Office 365. Hier sind die interessantesten Informationen aus KW 41. Blogs Join our Office 365 Champions Community Call October 17th Driving Adoption of Office 365 and Microsoft Teams Jira Cloud app now supports Jira Service Desk projects New! Confluence Cloud Messaging Extension in Microsoft Teams   Video Tech Tip: Microsoft Planner in Teams   Training Instructor-led training for Microsoft Teams   Dokumentation Create an org-wide team in Microsoft Teams Dynamic membership rules for groups in Azure Active Directory Use Microsoft Teams scoped directory search Cloud Video Interop for Microsoft Teams   Mobile Microsoft Teams for iOS - version 1.0.56   Viel Spaß mit Microsoft Teams!   Sie interessieren sich für Microsoft Teams? Dann werden Sie Mitglied des Microsoft Teams Meetup Berlin.       

Das Blog Cumulative Update für September 2018 (CU0918) fasst interessante Themen rund um Cloud Sicherheit, Exchange Server, Office 365, Microsoft Teams, Azure und Skype for Business des Monats September 2018 zusammen. Exchange Server Outlook License Requirements for Exchange Features Web Management Service (WMSvc) could not be started: 2147483640 Enable MAPI over HTTP Announced: improvements to Hybrid Publishing and Organization Configuration Transfer Announced: improvements to Hybrid Publishing and Organization Configuration Transfer Microsoft 365 | OneDrive | Exchange Online | and more [STICKY] Office 365-Trust Center [STICKY] Office 365 URLs and IP address ranges Office 365 Support and Recovery Assistant (aka SaRA) Outlook 2016 support in Office 365 after Oct 13, 2020 OneDrive Message Center Updates August 16th-August 31st When Things Go Wrong in the Cloud It’s Hard to Look Where for Help Enabling Access to Teams for Guest Users with PowerShell What that BOXServiceAccount Does in Office 365 Public Folder Sync–Duplicate Name Error Office 365: Stale Information in the Offline Address Book and Individual Contact Cards Office 365: Challenges with Distribution Groups for Migrated Mailboxes and a Script Based Solution OneDrive Announcements at Ignite 2018 Microsoft ...

In Legacy Public Folder World with Exchange Server 2010 it was pretty easy to find the parent path of email enabled public folder: (Get-MailPublicFolder MAILADRESS | Get-PublicFolder).ParentPath   Problem When you try the same approach with modern public folders using Exchange Server 2013+ EMS, you receive an error. Get-MailPublicFolder MSTeamsPF@varunagroup.de | Get-PublicFolder Cannot process argument transformation on parameter 'Identity'. Cannot convert the "varunagroup.de/Microsoft Exchange System Objects/MSTeamsPF" value of type "Microsoft.Exchange.Data.Directory.ADObjectId" to type "Microsoft.Exchange.Configuration.Tasks.PublicFolderIdParameter". + CategoryInfo : InvalidData: (MSTEamsPF:PSObject) [Get-PublicFolder], ParameterBindinmationException + FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-PublicFolder + PSComputerName : P01.varunagroup.de   Solution You need to use the EntryId paramater of the Get-MailPublicFolder result. $pf = Get-MailPublicFolder MSTeamsPF@varunagroup.de Get-PublicFolder -Identity $pf.EntryId Name Parent Path ---- --------- MSTeamsPF \Modern Collaboration Get-PublicFolder does not take pipeline inputs.   Links Find parent path for email activated Public Folder   Enjoy modern public folders :-) 

When you install a Cumulative Update for Exchange Server 2016 you might receive the following informational message: MAPI over HTTP, the preferred Outlook desktop client connectivity with Exchange server, is currently not enabled. Consider enabling it using: Set-OrganizationConfig -MapiHttpEnabled $true For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarnMapiHttpNotEnabl ed.aspx This modern protocol for Outlook has been introduced to Exchange Server with Exchange Server 2013 SP1. The protocol removes the dependency to the Windows Server RPC over HTTP component. The reduced complexity enhances the reliability of the client access protocoll. It's available for quite some time now.  You can enable MAPI over HTTP on the organization level using the following Exchange cmdlet: Set-OrganizationConfig -MapiHttpEnabled $true You can still controll the protocol setting at the user level by deactiviting MAPI of HTTP for certain users, if required: Set-CASMailbox -Identity [USER] -MapiHttpEnabled:$false If your IT infrastructue is still not ready for MAPI of HTTP, your IT components pretty outdated. It's time to move forward and to modernize the infrastructure.  NOTE Did you know that MAPI over HTTP connects to Exchange Server using TLS to encrypt the connection? Even though that the protocol name is "overHTTP" it literally uses HTTPS ...