Azure SQL MANAGED INSTANCE error 80071bc9. [CFabricCommonUtils::GetFabricPropertyInternalWithRef] EndGetProperty call failed for property: SpaceToReserveInMB with result: 80071bc9

Do you use Fabric Link or any other Fabric-related feature? (I mean the error message points to so something Fabric-related.)

To me this does not sound right, but something Microsoft should investigate. I would advice you to open a support case through the portal. Depending on your support policy, you may still end up here in Microsoft Q&A, but Microsoft support staff will have to pick it up, and possibly escalate it to the product group after investigations.

Thanks Erland for your response.We tried to locate more errors or logs related to the Fabric link but no clue at all. We tried to get the Microsoft support via our partner: Crayon (now SoftwareOne) but they refused to provide due to they consider is a Microsoft vendor issue.... what to say!
Thanks

Hi @Jorge

Sorry about the partner runaround. On the documentation point, there isn't an official "keep X% free" number for Managed Instance, and I'd rather be straight about that than invent one. What the docs do define is the mechanism that bites you, and it explains the 84 to 90% pattern.

On Managed Instance, storage usage is counted as allocated file sizes, including tempdb and every log file. The limits docs say tempdb can grow up to 24 GB per vCore, but only within the currently available instance storage, which is defined as reserved size minus used space. The same applies to log file growth. So once allocated space gets close to the limit, a tempdb or log autogrow fails, and that's when connections start failing instance-wide even though your data files look fine. Backups don't take instance storage at all, PITR and LTR go to separate backup storage, so your retention settings aren't the trigger.

The one change that addresses it:

1. Give the instance real headroom by increasing reserved storage from Compute + storage. Storage-only changes are online with no failover. Aim to keep allocated space comfortably below the limit, with room for tempdb at its 24 GB per vCore maximum plus your largest log file's normal growth.
2. Watch it with this on each instance, and alert at around 75%:

   SELECT TOP 1 reserved_storage_mb, storage_space_used_mb,
          CAST(storage_space_used_mb*100.0/reserved_storage_mb AS decimal(5,1)) AS pct_used
   FROM master.sys.server_resource_stats ORDER BY end_time DESC;

The Fabric property error you quoted is an internal platform lookup, so only Microsoft can read what happened behind it. If you want that investigated, a CSP partner is required to provide support for subscriptions they sell and can escalate to Microsoft through Partner Center, so it's fair to push back on Crayon. Moderators here can also pass your instance details to the product team by private message.

Could you check the error log around 23:32 for errors 1105 or 9002, and let me know whether these are General Purpose or Business Critical instances? That confirms which file hit the wall.

If this helped, please click Accept Answer so others hitting this at high storage usage can find it.

Reference: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/resource-limits