
# Energy & environmental compliance on Azure

Compare documented Energy & environmental compliance deployments on Azure, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/azure/energy-environmental-compliance/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Subscription and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal (checked 2026-11-20).
- Network: Virtual Network (VNet)
- Identity and access: Microsoft Entra identities and Azure RBAC
- Installation guidance: Bicep/ARM templates or Terraform; review deployment scope and role assignments.
- Guidance source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview
- Guidance reviewed: 2026-11-10


### Private offers

Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment.
Source: https://learn.microsoft.com/en-us/marketplace/private-offers-overview (reviewed 2026-11-14).

### Private connectivity

Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability.
Source: https://learn.microsoft.com/en-us/azure/private-link/private-link-overview (reviewed 2026-11-14).

### Cross-tenant operations

Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor.
Source: https://learn.microsoft.com/en-us/azure/lighthouse/overview (reviewed 2026-11-14).

### Government environments

Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government.
Source: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome (reviewed 2026-11-14).

The listings below have evidence for Microsoft Azure. Read each cloud evidence note for the applicable package, edition and support qualifications.

2 listings.


## EarthSoft EQuIS Enterprise — Self-Hosted

Self-hosted environmental data management with compliance monitoring, data validation, workflow automation and reporting.

- Listing: https://launchinyourcloud.com/directory/earthsoft-equis/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary EarthSoft server and Active Client Access licenses; external viewer/service-provider terms differ
- Licensing model: commercial-only
- Installation: Licensed Enterprise installation on Windows Server/IIS and SQL Server, or the documented Azure Web App deployment
- Architecture: Persistent ASP.NET web application and workflow services backed by Microsoft SQL Server or Azure SQL Database
- Operations: Customer operates application hosting, database, network access, backups, user roles, licenses and upgrades. Obtain the installers and supported build details from EarthSoft.
- Product website: https://earthsoft.com/products/equis-hosting-options/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Enterprise rather than EarthSoft-operated EQuIS Online. The official Azure installation guide deploys into client-managed Azure Web Apps and configures the database and licenses. Internal users and externally exposed viewers have different licensing arrangements. Review integrations and choose a supported build before installation.

The documented Enterprise server and named-user licenses are commercial. EarthSoft’s published example EULA identifies EQuIS as proprietary software; confirm the actual contract and external-user entitlements.

Windows/IIS or continuously running Azure Web App services with persistent database storage. The Azure guide enables Always On; this is a server-based application deployment.


### Category fit

- energy-environmental-compliance: Environmental data collection, validation, compliance monitoring and reporting for air, water, soil, waste and related project data.

- data-analytics: Environmental data quality checks, reporting, visualizations and configurable dashboards; its scope is environmental and geotechnical data rather than general-purpose BI.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.earthsoft.com/ent-new_installation_azure.htm (checked 2026-11-12). 


### Cloud deployment evidence

- EQuIS Enterprise application installation on Azure (azure): https://help.earthsoft.com/ent-new_installation_azure.htm
  EarthSoft documents creation and configuration of an Azure Web App and deployment of the licensed EQuIS Enterprise application package, rather than only an Azure SQL database. This is the customer-hosted Enterprise path; obtain the compatible package and required licenses from EarthSoft.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Enterprise installation prerequisites and installer: https://help.earthsoft.com/ent-new_installation.htm

- Client Azure Web App installation: https://help.earthsoft.com/ent-new_installation_azure.htm

- On-premises and hosted deployment options: https://earthsoft.com/products/equis-hosting-options/

- Environmental data and reporting scope: https://help.earthsoft.com/equis-introduction.htm

- Current runtime and database requirements: https://help.earthsoft.com/equis7-hardware-system.htm

- Server and named-user license model: https://help.earthsoft.com/ent-equis-licenses.htm

- Published example proprietary EULA: https://help.earthsoft.com/EQuIS%20EULA%20Example.pdf

### Licensing sources

- https://help.earthsoft.com/ent-equis-licenses.htm

- https://help.earthsoft.com/EQuIS%20EULA%20Example.pdf

### Infrastructure sources

- https://help.earthsoft.com/ent-new_installation.htm

- https://help.earthsoft.com/ent-new_installation_azure.htm

- https://help.earthsoft.com/equis7-hardware-system.htm


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. EQuIS Enterprise documents browser OIDC login with a registered identity-provider application and redirect, plus an existing Enterprise account with matching identity and roles. Federation does not automatically grant repository access. This does not imply that separate Professional Browser Mode has the same authentication capabilities. Scope: EQuIS Enterprise OIDC user login; separate product surfaces retain their limits. Source: https://help.earthsoft.com/adm-openid-connect-auth.htm (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Enterprise 7 installation guide covers a Windows/IIS installation with an EQuIS SQL Server database, service account and network licenses. Use the licensed installer and the linked prerequisites; this is not a public Terraform or container artifact. Scope: EQuIS Enterprise 7 new installation; installer entitlement and current requirements must be checked. Source: https://help.earthsoft.com/ent-new_installation.htm (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The current hardware/system page lists supported Windows, SQL/database and runtime dependencies, but does not establish numeric Enterprise application/database CPU/RAM/storage sizing. Size ingestion, reporting, spatial widgets and HA beyond operating-system minimums. Scope: EQuIS Enterprise production hardware capacity remains unconfirmed. Source: https://help.earthsoft.com/equis7-hardware-system.htm (reviewed 2026-11-21).

- License pricing: Documented. Enterprise uses Server plus Active Client Access Licences, available as perpetual or term licences for internal users. External access has separate Viewer or service-provider agreements, and Enterprise 7 requires network rather than local keys for the described self-hosted licensing. Confirm the order and authorised server/user counts. Scope: EQuIS Enterprise 7 ACAL/server licensing; external-user and service-provider rights separate. Source: https://help.earthsoft.com/ent-equis-licenses.htm (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP S/4HANA EHS — Customer-Operated

Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.

- Listing: https://launchinyourcloud.com/directory/sap-s4hana-ehs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements
- Licensing model: commercial-only
- Installation: Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides
- Architecture: SAP S/4HANA application stack with SAP HANA database and EHS Fiori applications
- Operations: Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.
- Product website: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The on-premise edition is explicitly customer-installed and customer-operated. This entry covers its EHS components, not SAP-managed Cloud Private Edition or Public Edition. Check the selected release, component entitlements and implementation scope. Environmental reporting still requires configured requirements and reliable source data.

The listed on-premise edition uses SAP commercial software licensing. The official deployment comparison describes its perpetual-license model; the customer agreement defines the exact component rights.

Customer-operated SAP application and HANA database services run on provisioned infrastructure. This is the on-premise edition, separate from SAP-managed cloud services.


### Category fit

- energy-environmental-compliance: Environmental requirements, emissions calculations, compliance scenarios, deviations and reports for environmental authorities.

- incident-investigation-management: Safety incident and near-miss capture, investigations, root-cause classifications and follow-up actions. This is industrial EHS scope, rather than a general legal investigation platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp (checked 2026-11-12). 


### Cloud deployment evidence

- Customer-provided SAP S/4HANA deployment on AWS (aws): https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html
  AWS Launch Wizard provisions customer resources and can install customer-provided SAP S/4HANA software. Evidence covers the underlying S/4HANA platform; confirm EHS licensing, supported sizing, database and SAP release before deployment.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA infrastructure deployment on Azure (azure): https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana
  Microsoft documents S/4HANA infrastructure in a customer Azure subscription. Evidence covers the platform hosting option; confirm EHS modules, SAP licensing, supported operating systems and software installation separately.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA reference architecture on Google Cloud (gcp): https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp
  Google documents S/4HANA on SAP-certified Compute Engine infrastructure. This is platform hosting evidence; EHS functionality, licenses and supported SAP configurations still require confirmation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated on-premise installation and operations: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest

- Environment Management scope: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/1b3596cc5dd5428d887966a4193ddc29/6d08555321d77d77e10000000a441470.html

- Current incident-investigation configuration: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/f5d3e1005efd4e86acf9a65abf428082/96e81bbdc3c54a70b3b374b182bb87c0.html?locale=en-US&version=2025.000

- Commercial model and deployment responsibilities: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Licensing sources

- https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Infrastructure sources

- https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed EHS and deployment material does not establish the selected application UI, release and complete identity configuration. SAP platform authentication options require the actual Fiori/ABAP/GUI entry points and compatible identity components; do not infer a ready EHS federation setup from a generic SAP capability. Scope: Customer-operated S/4HANA EHS identity deployment remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. AWS Launch Wizard can provision SAP landscapes and install customer-provided supported S/4HANA software, including separate multi-instance/HA patterns. Supply licensed installation media and validate supported releases. This is underlying S/4HANA platform automation; EHS activation, business configuration and data migration remain separate. Scope: Provider-documented S/4HANA deployment supporting the EHS parent platform; not a packaged EHS solution. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21). Deployment artifact: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html. Artifact reference: Current AWS Launch Wizard supported SAP deployment guide.

- Minimum footprint / sizing: Sources checked — unresolved. Launch Wizard selects resources from supplied SAP requirements; it does not establish an EHS-specific capacity baseline. Obtain certified S/4HANA/HANA sizing for application/database memory, batch/analytics, data volume and HA rather than interpreting supported maximum memory as a minimum. Scope: S/4HANA EHS workload sizing remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- License pricing: Documented. SAP distinguishes customer-managed S/4HANA on-premise perpetual licensing from subscription-based Private Edition with SAP technical managed services. Do not substitute a cloud subscription for the customer-operated scope; EHS module rights and implementation pricing require the actual agreement. Scope: S/4HANA on-premise deployment model; not a module-specific EHS quote. Source: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5 (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






