Exchange Online Mailbox only has 25gb Storage Quota

Some of my customers mailboxes were still displaying 25gb as their mailbox storage quota size instead of 50gb.

 So the fix is quite simple.
Firstly connect to Exchange Online via Powershell.
1. Set-ExecutionPolicy unrestricted
2. $LiveCred = Get-Credential
3. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection
4. Import-PSSession $Session
Then run the following CMDlet which will increase the size to 50gb for all user mailboxes:
Get-mailbox -resultsize | Set-Mailbox -ProhibitSendReceiveQuota 50GB -ProhibitSendQuota 49.75GB -IssueWarningQuota 49.5GB

External recipients don’t receive email messages that are send to a distribution group in Exchange Online.

During one of my recent migrations from an on premise Exchange to Office 365 some people complained to me that some distribution group members didn’t receive messages send to this distribution group.

During my tests I’ve noticed that the external Anti-Spam solution didn’t accepted the messages he received for the external recipients. I also noticed that the sender was not getting any non-delivery reports.

After some investigation I found out that the distribution group parameter “ReportToOriginatorEnabled” in Exchange Online by default is set to False, which is different from the on premise Exchange version where this parameter is by default set to True.

To fix this behavior I used PowerShell:

Set-DistributionGroup “<DistributionGroupName>” – ReportToOriginatorEnabled $true

More info:


Submitted by Bart Roels – – @FomeZ

SharePoint Document Management – Facts about versioning

Main selling point

Versioning has always been one of the main selling points for SharePoint Document Management. At least, that’s what I always use as an, there are more of course, argument for storing documents in SharePoint instead of file shares. While I was preparing my presentation about Best Practices: Document Management in SharePoint 2013 for SharePoint Connections Amsterdam 2013, I started to wonder if versioning worked as well as I thought it did. Let’s take a closer look.

New versions

When are new versions actually created in SharePoint? A new version is created when you:

  1. Upload a new document
  2. Upload document with the same name
  3. Change the properties of the document
  4. Open, edit or save the document

Upload a new document

The first version is created when I upload a new document into a SharePoint document library:

Upload document with the same name

What happens if I upload the same document again? The following pop-up appears:
Yes, I am sure! So I click on Replace it:
The document is now version 0.2.

Change the properties of the document

Let’s change the name of document:
This also results in a new version:
Please be careful! Even without actually changing the properties but clicking on Save results in a new version.

Open, edit or save the document

This one makes sense of course so after I open the document in the browser and edit some text a new version is created:


What about co-authoring? Working together with multiple people in the document, how does this impact the versioning? This is the official answer from Microsoft:

“During co-authoring of a document, when a different user begins working on the document or when a user clicks save to upload changes to the library. The default time period for creating new versions during co-authoring is 30 minutes, but an administrator can change that setting.”
I actually tried this in my Microsoft Office 365 demo tenant but without success. After staying in the document, with multiple users, for over 30 minutes no new versions were created. Unfortunately I cannot test this in an on-premises SharePoint site.

Does it work?

To be honest, that really depends on your situation and business requirements. Let’s take a look at my work situation:
I write project proposals together with a technical specialist, project manager and account manager. I create the proposal and for me its now version 0.1. After I am done, this can take multiple days, I create version 0.2 and hand the document over to the technical specialist. He or she writes her part of the proposal and turns it into 0.3 before handing it over to the project manager. After the project manager and the account manager are done, the proposal is at 0.5 and can be send to the customer as version 1.0.
This doesn’t work with SharePoint versioning because SharePoint keeps creating versions after I continue working the next day and after I close and reopen the document. You can have more control with versions. You have to work with check-in and check-out. The only downside is that it disables co-authoring.
Please really take a look at your or your customers, or your own, requirements around versioning to see if SharePoint versioning works.

Time to patch your Office 2013/Pro Plus: ms13-104

The token security issue reported in May 2013 (Read the full story on, that Office Pro Plus could be tricked in sending out it’s token for Office 365 while talking to a malicious site. Through that mechanism users tokens could be collected and be used for easy access to the users data, mailbox, …

The resolution is finally released as a part of the automatic updates of Windows/Office. You can download the patch on if you only want to deploy this one.

I urge you to install it as soon as possible.

Read also Paul Robichaux’ blog post about the topic:

The influence of Activating SharePoint Server Publishing Infrastructure on Security Trimmed Navigation

Security and Navigation, it’s something we need to be really careful with. it’s really frustrating seeing navigation items where you don’t have access to and it’s even more annoying to not see your navigation even though you have access to the library or to one of the items in it. According to the technet article giving access to an item is a SharePoint Library for a certain user will result in the assignment of Limited Access on the top levels to

“is to allow enough access to the object hierarchically above the uniquely permissioned item so that the Object Model (OM), master pages, and navigation can display when the user attempts to navigate to the item. Without the Limited Access permissions at the parent scopes, the user wouldn’t be able to successfully browse to or open the item that has unique permissions.”

This results in:

IIustrates object hierarchy for a document library, in which all objects but one inherit their scope from their parents.


IIustrates how the hierarchical depth of scopes can affect the amount of work required to add Limited Access users to parent scopes.

Let me transform this into a Real Case Scenario:

We have a Document Library Finance where only the CFO and his team have access to. In the current navigation (left side menu) only the CFO and his team will see the Document Library Finance. Every other employee will not see it since they don’t have access to the Library or to any document in that Library.

One document Expenses.xlsx must be editable for every user since they have to add their expenses in that spreadsheet. So the CFO assigns everyone with Contribute rights. As mentioned in the technet article everyone will receive Limited Access rights on the Library. In SharePoint 2013 limited access rights are not shown in the Permission Overview to avoid any confusion like we had in SharePoint 2010. So Far So Good, everyone can see the library Finance.

Since we want to incorporate some publishing features like Master Pages, Page Layouts, … we need to activate SharePoint Server Publishing Infrastructure. At that exact moment the library Finance disappears from the Current Navigation. It is only visible to the CFO and his team. The document Expenses.xlsx is only available through a direct link or when used by the WebPart/AppPart Finance. 

Deactivating the feature doesn’t rollback the damage. So Be Very Careful. Since it occurs in SP On Premises & Online I doubt it that it’s a bug but a change/feature/opportunity in the platform. In my humble opinion a bad one. I’m still hoping it’s a bug. I’m also hoping pigs can fly and hell freezes over, …

I’ve made a screen cast of a similar process which you can find on YouTube : ..

Resources/Room mailboxes, automatically decline meeting if there is a conflict

When we create a room mailbox, we can define if the room uses delegates or does an auto accept when possible. We can define a basic setting during the creating of the room mailbox. Do to define a resource mailbox, go to Admin > Exchange > Recipients > Resources  and click on the +


When we edit the Room mailbox we have more settings.


But there is one little caveat. In this scenario every conflict will result in a Tentative instead of a Rejected meeting. The reason for this behavior is a little parameter called: AllRequestOutOfPolicy. By default this parameter is true. This effectively treats all conflicts as “Out Of Policy” and requires delegate approval for the meeting to be scheduled. This causes the “Tentative” email response.

You can only change this by using PowerShell.

Set-CalendarProcessing “Name of Room” -AllRequestOutOfPolicy $False

This sets it to false and automatically sends a declined email to the meeting requestor for all “Out of Policy” Meeting requests, which includes conflicts.