Reliability in Sustainability data solutions in Fabric
This article describes reliability support in Sustainability data solutions in Fabric, covering intra-regional resiliency via availability zones and multi-region deployments.
Sustainability disclosures, analytics and reduction require rich environmental, social, and governance data that originate from disparate sources and need to be unified to improve its efficiency and value. Sustainability data solutions in Microsoft Fabric provide unique capabilities to ingest, harmonize, and process disparate data for specific sustainability scenarios.
The reliability guidance for most of these capabilities are covered by the Microsoft Fabric reliability guide. However, that document does not include reliability guidance for the ingestion of data in Microsoft Azure emissions insights. This guide focuses specifically on the resiliency of data ingestion process for the Microsoft Azure emissions insights platform. After your emissions data is loaded into your Microsoft Fabric instance, you can consult the Microsoft Fabric reliability guide for the rest of the reliability guidance.
Transient faults
Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. They correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
If a transient fault occurs during ingestion of emissions data, you must manually trigger the job again. You can monitor the ingestion job from the Microsoft Fabric monitoring hub.
Availability zone support
Sustainability data solutions in Fabric is zone-redundant by default.
Region support
Zone redundancy for the emissions data source is automatically enabled when you use any region that supports availability zones.
Cost
There's no additional charge for zone redundancy.
Zone-down experience
The Sustainability data solutions in Fabric platform is responsible for detecting a failure in an availability zone. You don't need to do anything to initiate a zone failover.
A zone failure isn't expected to cause any data loss or downtime to your resources.
Multi-region support
Internally, Microsoft's Cloud for Sustainability services are partially geo-redundant. If a major region failure occurs, emissions data can be reconstructed in another region.
Region-down experience
During a region failure, Azure emissions data that's already ingested into Fabric is accessible as long as Microsoft Fabric is available. For information on how to plan for disaster recovery and configure multi-region support in Microsoft Fabric, see Reliability in Microsoft Fabric .
Ingestion of new Azure emissions data, as well as any missing data, resumes after Microsoft restores services into the region. Although the process of ingesting new and missing data might take several days, previously ingested data is still available.