• We have a client wit a couple of Exchange 2013 databases that have been automatically excluded from provisioning because of a lack of space.

    Unfortunately I have been unable to find the minimal amount of required free space. Does anyone know the minimum amount of free space required? The disks containing the affected databases all have around 10% of free disk space at the moment.

    Thursday, April 20, 2017 3:07 PM

All replies

  • That parameter is not applicable in environments with Exchange Installed On-premise.

    That is a Microsoft Internal Parameter which they will use for managing Tenants using Microsoft Cloud services.




    This parameter is reserved for internal Microsoft use.

    Can you ping the output of the cmd below which is run against 1 or 2 DB's against which we have space constraints ?

    Get-MailboxDatabase DatabaseName -Status | fl Name,DatabaseSize,AvailableNewMailboxSpace

    AvailableNewMailboxSpace is the property which will give the information about the Freespace which can be fragmented or reclaimed after the DB is Defragmented. But Defrag on DB's on Exchange 2010 Later versions is not recommended. So, you could consider creating a new DB and move the mailboxes over to the NEW DB.

    Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

    Friday, April 21, 2017 12:38 PM
  • Hello Stephan,

    Base on my experience, there're lots of factors which relate to disk quota, for example: database copy, number of mailbox, mailbox size, the mount of message per day, the average size of message for inbound and outbound and log file.

    By default, the value of IsExcludedFromProvisioning is false, also IsExcludedFromProvisioningBySpaceMonitor is True. If server disk monitor that there's no sufficient free disk space, IsExcludedFromProvisioning will be automatically set to True.

    Therefore, to fix your issue, it's recommend to increase your driver disk or split those database into separate disk, for example add 200G per disk driver.

    Best Regards,

    Allen Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Friday, April 21, 2017 1:05 PM
  • Hi Allan,

    Every database has it's own disk. 

    We have 4 volumes all between 300 and 400 GB with 1 database per volume. Every volume has 6 to 13% of free disk space. 

    Adding space to the disks seems logical to me, I had the same idea. The client however pays per GB of storage so we need to explain to them why they would need the additional space. Is there any source we can quote what the minimum amount of free space needs to be?

    Friday, April 21, 2017 2:19 PM
  • It's too smaller if there's only 6% - 13% free disk for each volume.

    You can run below command in Exchange to check the database health status:
    Get-ExchangeServer | Get-Serverhealth -HealthSet Diskspace | ? AlertValue -ne Healthy | ft –autosize

    In Exchange 2013 SP1, the default threshold for the low volume space monitor is 200 GB, and in Exchange 2013 Cumulative Update 6 and later, the default threshold is 180.

    Thus, we need to increase the free space available on the database and log drives.

    Or, we can use below command to modify this threshold (its in MB not GB):
    Add-GlobalMonitoringOverride -Item Monitor –Identity MailboxSpace\StorageLogicalDriveSpaceMonitor 
    -PropertyName MonitoringThreshold -PropertyValue 102400

    Best Regards,

    Allen Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    • Proposed as answer by bangera Monday, March 12, 2018 1:43 AM
    Tuesday, April 25, 2017 1:09 PM
  • Hi Allen,

    I changed the MonitoringThreshold to 10 GB a couple of weeks ago. 

    Managed availability says all is healthy however we still have the IsExcludedBySpaceMonitoring set to True. This just doesn't make any sense.

    Wednesday, April 26, 2017 7:10 AM
  • Dear Allen,

    Are you sure that the Property value in the above command is in MB and not GB? I saw a couple of articles which have updated the property value in GB.

    Can you please clarify?



    Maaz Siddiqui

    Sunday, March 11, 2018 9:34 AM