20 May 2020
Microsoft is continuing to add 3rd party storage providers to Microsoft Teams, with the next one being Egnyte which will rollout to all customers in mid-June as part of 63706. Microsoft is enabling this storage provider by default. If your organization implements data policies which allow for only certain storage providers to be leveraged in your environment, this is problematic – since features rollout gradually, there is no specific date in which an administrator can turn this off from the Teams Admin Center.
There is a workaround, however. You can disable it via PowerShell today using the SkypeOnlineConnector module. Download and install the SfB Online module, then run the following PowerShell cmdlets.
Accounts without MFA enabled:
Import-Module SkypeOnlineConnector
$cred = Get-Credential
$sess = New-CsOnlineSession -Credential $cred
Import-PSSession $sess
Set-CsTeamsClientConfiguration -AllowEgnyte $false
Accounts with MFA enabled:
Import-Module SkypeOnlineConnector
$sess = New-CsOnlineSession -UserName admin@contoso.com
Import-PSSession $sess
Set-CsTeamsClientConfiguration -AllowEgnyte $false
Once set, Engyte will be disabled by default when the feature rolls out to your tenant.
12 May 2020
The SharePoint 2019 May 2020 Updates have been released.
For all SharePoint updates, visit SharePoint Updates.
12 May 2020
The SharePoint 2016 May 2020 Updates have been released.
For all SharePoint updates, visit SharePoint Updates.
28 Apr 2020
The SharePoint Patch Script has been published to the PowerShell Gallery. Now you can run Install-Module SharePointPatchScript from PowerShell instead of downloading it from GitHub! Hopefully everyone find this a convenient way to download and keep the module up-to-date.
Enjoy!
27 Apr 2020
Today, Microsoft announced the deprecation of SharePoint Designer custom forms in SharePoint Online, directing individuals to instead use PowerApps for custom form scenarios.
The deprecation was immediate with no notice. There also isn’t any information as to why, but I would suspect an immediate removal would be due to a potential security issue, similar to the SharePoint 2010 workflow remote code execution vulnerability which allows an application installed on a SharePoint Server to be run in the context of the IIS Application Pool user – in other words, it is likely a significant security issue.
If there is a patch or global setting to remove SharePoint custom forms in SharePoint Server within the next two months, that will tell us :-)
As always, I recommend those venturing into SharePoint Online to avoid “legacy” SharePoint functionality, such as SharePoint 2010 or 2013 workflows, InfoPath, classic sites, and so on.
Here is the complete notice.
Awareness: SharePoint Designer feature deprecation
MC210713, Stay Informed, Published date: Apr 25, 2020
We’ve identified an issue affecting SharePoint Designer
We’ve identified an issue affecting SharePoint Designer functionality for creating and editing custom Forms within SharePoint Online. After careful examination, we’ve determined that there is no known fix for this issue and have elected to disable the feature effective as of 3:00 AM UTC on Saturday, April 25, 2020.
Users who have previously leveraged SharePoint Designer to create custom Forms are instead able to utilize PowerApps for this purpose.
PowerApps is an easy and powerful tool that allows users operating in the SharePoint Online Modern experience to create and edit custom Forms for SharePoint lists and document libraries right from a browser window. PowerApps does not require traditional coding knowledge or any additional app downloads such as InfoPath.
*Note: SharePoint Online Classic users will need to temporarily switch to the Modern experience to access and utilize PowerApps; though, all custom Forms created in PowerApps are accessible by SharePoint Online Classic experience users.
Additional information