This happen all the time, you are sending an email and by the time you hit the Send button, you realize you have sent it to the wrong recipient(s).
With Exchange we all know (or should know) the recall feature but there is an important limitation: this works ONLY if the recipient(s) is/are hosted in the same Exchange organization and the message is not yet read.
So, what do we do if the message has been already processed and sent out; you try the recall (which means the recipient will receive the automatic message saying your tried to recall) but it will failed anyway to remove/delete the message.
Now, with Office 365 / Exchange Online you can undo a sent email for up to 30 seconds. Which means the sending action will be delayed up to the period defined.
To enable this new feature, logon to Outlook on the Web (formerly known as Outlook Web Access) and go to your settings to reach the Mail\Automatic Processing\Undo sent and select the time to allow the cancellation.
Once you have activated the Undo sent feature, next time you will send an email, the mail will not be sent immediately, instead it will be saved in the Draft folder for the period you have defined and only once the delay has been reached it will be sent.
This means if you want to retract this mail, you just have to go to your Draft folder and hit the Undo action button shown on top right of the folder view, which then will convert the mail to a draft.
IMPORTANT this works ONLY from Outlook on the Web
While upgrading my SharePoint environment from 2013 to 2016, I ran into an interesting issue with content database upgrade.
I have deployed a fresh new SharePoint 2016 running on Windows Server 2016 and then perform the classic detach/attach upgrade process to migrate the content from the SharePoint 2013 environment.
One of this content DB is hosting only one site collection, but this site collection is NOT a root site collection.
When running the attach command on SharePoint 2016 (Mount-SPContentDatabase) which performs the upgrade to 2016, I got no error but there was no site collection available.
After some time, tests and research, I found that if the content database does not contain a root site collection, then the attach/upgrade process makes the site collection unavailable.
As solution, create a temporary web application on you SharePoint 2013 environment, attach the content database to it and create a root site collection. Then on SharePoint 2016, create another temporary web application and then run the Mount-SPContentDatabase. Once completed, you can delete the root site collection and detach the content DB to attach it to the appropriate web application.
When Microsoft has introduced Microsoft Team, this was only manageable at the organization level.
Now, Microsoft Teams is now user based licensed; meaning you can now enabled/disable it on a per user basis
And if use a PowerShell script to automate (or bulk update) licensing options, the service plan is TEAMS1
as of today, my hosting platform is now running on SharePoint 2016.
You should not notice any change
This has been a gap in Office 365 and SharePoint Online for quite some time: there was very few way and options to manage OneDrive for Business.
Good news, this gap is going to be filled, maybe not yet with everything you may be looking for but at least an administration console for OneDrive for Business.
If you want to start to take a look, go to https://admin.onedrive.com/ (yes, there is not yet any integration with Office 365 admin portal or SharePoint Online administration center).
From there you will be able to manage the sharing, the synching (caching) options and compliance.
If you already had configured some of these settings (like sharing options or synching) mostly with PowerShell, their value will be set automatically from your previous configuration.
It will clearly makes things easier to manage.
This is really an early first release preview – quite redundant – as I think one important thing is missing: a simple and clear reporting for who has provisioned his OneDrive for Business and the storage consumed. Hopefully this will come
Following my previous post regarding the Cloud Management Point gateway feature introduced with the fast channel current branch update (see http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=838), another new “cloud” feature has been introduced called Cloud Distribution Point. As with the Cloud Management Gateway, this will help managing internet based client with SCCM.
This new feature will make your internal distribution point(s) available to the internet client based using Azure.
NOTE if you already have enabled the Cloud Management Gateway as per my previous post, you can bypass this step
From the console, access the Update and Servicing section to download and install the update
When installing the update, ensure you enable the Cloud Management Gateway feature
Before starting you will need to request a new certificate to include the cloudapp.net namespace.
NOTE if you already have enabled and configured the Cloud Management Gateway, you need to define another cloudapp.net namespace which will need to be included in a certificate. Certificate which will be used as a management certificate (export to a .CER file) as well as to provision the Azure piece (export to a .PFX file)
Then from the SCCM console, go to the Administration\Cloud Services\Cloud Distribution Points to create the new gateway.
The process is pretty straight forward
Provide the Subscription ID and the management certificate (the new one with cloudapp.net in a .CER and .PFX format) – the CER file will be uploaded into the Azure subscription while the PFX will be imported into SCCM with the wizard.
You can get the Subscription ID from the Azure portal
Select the correct FQDN (*.cloudapp.net) to generate the service name as well as the Region where the VM will be provisioned and the SCCM site server to use as master
Once the cloud distribution point is provisioned (status Ready in the console) it will become an available distribution point
You can then associate it with a distribution group and/or select it as DP when deploying your packages.
The fast channel of the current branch 1610 of System Center Configuration Manager (SCCM) got an interesting update which deliver the Cloud Management Gateway.
This new feature will help to reduce the infrastructure complexity to manage internet based client.
NOTE if the update is not displayed in the Update and Servicing section, you may not have enabled the fast channel. To do this, download the script available here https://gallery.technet.microsoft.com/ConfigMgr-1610-Enable-046cc0e9
Then from the SCCM console, go to the Administration\Cloud Services\Cloud Management Gateway to create the new gateway.
NOTE if you do not upload the certificate into Azure, you will get an error “The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription”
To define the VM creation details you need to import again the certificate (PFX file); you may got a pop up being displayed “The service certificate has the following errors/warnings.”, do not be afraid this is because you generates your certificate with the SCCM server name, you will be able to select the service FQDN after the import which will generates the service name correctly
Select the correct FQDN (*.cloudapp.net) to generate the service name as well as the Region where the VM will be provisioned
You can uncheck the Verify client certificate revocation, unless your internal CA is publicly published
The next settings define the alert thresholds; keep it as default or change it to match your need
After the usual configuration summary you can complete the creation process; you will to wait some time to get the VM provisioned on your Azure tenant; you can check the progress from the SCCM console
Once the Cloud Management Gateway status is provisioning completed in the SCCM console, you can continue to configure the gateway
To do so, you need to define a connection point with the Cloud Management Gateway by adding the new server role “Cloud management gateway connection point”
Once you have enabled the cloud management gateway connection point role, you need to update your management point to take advantage of the new role
At this stage, the status of the Cloud Management Gateway is now Ready and you can see the connection point(s) using the Connection Point tab (the status is Disconnected if you do not have yet enabled the management point)
Once the connection point status is Ready, you can also see the role endpoints associated with the gateway
Once you have configured the gateway, you should see your Internet based client using the new Internet-based management point which will be something like <your Cloud Management Gateway service>.cloudapp.net/CCM_Proxy_MutualAuth/<GUID>
Starting January 2017, when a Yammer group is created a corresponding Office 365 Group will be automatically provisioned at the same time.
The rollout is expected to be completed by March 2017.
After a little bit more than a month in preview, Microsoft has announced the general availability for Azure AD PowerShell v2.0
This new version does not provide (yet) full functional parity with the older Microsoft Online module.
The current Microsoft Online PowerShell module will not be updated anymore.
You can get more details about what is included in this version 2.0 here https://docs.microsoft.com/en-us/powershell/azuread/v2/azureactivedirectory while you can install it from https://www.powershellgallery.com/packages/AzureAD/18.104.22.168
The latest release of Azure AD Connect now officially supports SQL 2016 and Windows Server 2016, which also includes the ability to manage ADFS 4.0 (part of Windows Server 2016)
You can download the new release here https://www.microsoft.com/en-us/download/details.aspx?id=47594&751be11f-ede8-5a0c-058c-2ee190a24fa6=True
Benoit is specialized on Microsoft infrastructure (Active Directory, Azure, ForeFront products, Hyper-V, Identity Management, System Center, Windows) and collaboration (BPOS, Exchange, Office 365, SharePoint, Lync/Skype for Business) technologies.
He has been awarded as Microsoft Most Valuable Professional (MVP) since 2002 - on Windows, then SharePoint and finally Office 365. He has been recoginzed as Microsoft Community Contributor for his work on the Office 365 community in 2013 and 2014.
He has been involved in early stage of testing phase for many Microsoft products - from Windows to Office 365, including Exchange, SharePoint or Office client and WindowsUpdate.
He has participated as speaker or Ask The Expert (ATE) at many Microsoft or Quest events. He also participed in writing several books on SharePoint (2003 to 2010).
With more than 10 years of professional experience, he has a deep knowledge of the Microsoft market and his competitors.
This blog is using tracking code for analytics purpose.
No personal data are stored and maintained.