Azure AI Foundry

A customer can examine resource-level Azure emissions across all resource types, but reporting is monthly and does not isolate Foundry models or individual inference requests. For a deployment, request or export the selected service and region’s usage-linked footprint when available; do not treat company-wide renewable matching as per-request impact.

A customer can examine resource-level Azure emissions across all resource types, but reporting is monthly and does not isolate Foundry models or individual inference requests.

Monthly Azure emissions are based on billing and usage and can be reviewed at resource granularity, but do not isolate individual model inference, token counts, or water consumed by a request.

• What is Carbon optimization in Azure ↗

For Azure-hosted Models sold by Azure, Microsoft says prompts, outputs and customer training data are not used by model providers or Microsoft to train foundation models without permission/instruction. This is a hosting data-use commitment, not evidence about training corpus licenses. Select the model first and review its license plus corpus-provenance disclosures; prompt no-training terms do not clear the model’s original dataset.

Partner models and corpus provenance are outside this specific commitment and must be reviewed separately.

• Data, privacy, and security for Foundry Models sold by Azure ↗

Azure documents customer-selected geography for standard deployment and strong training restrictions, with broader processing in global/data-zone modes and storage in some stateful/abuse-monitoring cases. Check the exact API/web surface, plan, region, retention setting, routing, and stateful features in the applicable terms before sending sensitive content.

Azure documents customer-selected geography for standard deployment and strong training restrictions, with broader processing in global/data-zone modes and storage in some stateful/abuse-monitoring cases.

Actual deployment type, geography, feature and abuse-monitoring eligibility/configuration require confirmation.

• Data, privacy, and security for Foundry Models sold by Azure ↗

Some managed-compute deployments give customers more control, but the catalog also contains closed services and licenses vary. Check whether the chosen model’s weights and license permit inspection or relocation, and whether the serving runtime moves too; API compatibility alone is not an open stack.

Some managed-compute deployments give customers more control, but the catalog also contains closed services and licenses vary.

Catalog size and model cards do not establish open weights or data provenance for each entry; licenses and deployment control vary.

• Microsoft Foundry Models overview ↗
• Azure OpenAI Transparency Note ↗

Microsoft reports supplier findings and closure plans, but the reported scope is not specific to AI annotation and some plans remain open. Ask for current vendor-level pay, exposure, location, audit, and remediation records; a supplier code cannot substitute for worker outcomes.

Microsoft reports supplier findings and closure plans, but the reported scope is not specific to AI annotation and some plans remain open.

The published findings cover specified supplier audit scopes, not all suppliers, model evaluation labor, or all remediation outcomes.

• Microsoft Human Rights Transparency Report 2025 ↗

The company confirms defense-ministry Azure/AI use and a review supporting elements of serious surveillance-related reporting; it stopped specified services but continues others. Request the named contract and actual model/endpoint scope with enforceable use controls; do not treat ordinary government work or silence as proof of military use.

The company confirms defense-ministry Azure/AI use and a review supporting elements of serious surveillance-related reporting; it stopped specified services but continues others.

The report does not access IMOD customer content, does not establish the content/use of every service, and does not say the wider commercial relationship ended.

• Microsoft Summary of 2025 External Investigation and Follow Up ↗

If following this BNC campaign is a requirement, consider alternatives to paid Microsoft products where practical. Your selected model, cloud and billing route can introduce other companies into the purchase. This label follows the named company’s campaign status; it does not claim that BDS separately reviewed this exact product.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

Microsoft’s final 2026 review says Covington found evidence supporting elements of reporting about IMOD Azure storage and AI-service use, including Azure storage consumption in the Netherlands. Microsoft says it disabled specified subscriptions/services in September 2025 but continues providing IMOD with other Azure, Azure AI, software, and professional services. The report did not access customer content and does not establish all downstream uses.

Microsoft describes only selected service suspensions; the report does not establish all IMOD use, civilian impact, or the full scope of continuing services.

• BNC: live guide to consumer boycott and pressure targets ↗
• BNC: No Tech for Oppression, Apartheid or Genocide campaign ↗
• BNC: Microsoft campaign and subsidiaries guidance ↗
• Microsoft Summary of 2025 External Investigation and Follow Up ↗