Posts tagged with "Azure"

Microsoft-Decision-1 went GA in Microsoft Foundry on 9 October 2026 at $0.042 per million input tokens with free output, returning calibrated probabilities over fixed options instead of text, and it launched with an EU Data Zone at the same price as the US zone. We compare it with OpenAI's Decisions API and H2O-Lightning-4B, run the cost math for ticket routing and agent step-gating, and set out what Swedish buyers must record about its Qwen3.5-9B base.

Claude Haiku 5.5 is GA in Microsoft Foundry at $0.10/$0.50 per million tokens, the same Global Standard list price as GPT-6 Luna, and 90% below Haiku 4.5 on paper. The bills diverge on three lines: a tier that charges 5x on every token once a prompt passes 100K, a tokenizer that counts the same text as 30% more tokens, and an EU Data Zone that Luna offers at $0.12/$0.60 while Claude on Foundry has none.

Gemini 4 Argon launched on 30 September at an introductory $2/$10 per million tokens, the third frontier model at that price in three days, but unlike Claude Sonnet 5.5 and GPT-6.1 Sol it is not in Microsoft Foundry, has no API model ID, and goes to vetted cyber defenders first. The standard price is $4/$20 with no published end date for the discount, so Azure teams in Sweden should budget on the higher figure and prepare a gateway route rather than switch now.

Claude Sonnet 5.5 and GPT-6.1 Sol reached Microsoft Foundry a day apart at the same $2/$10 list price, yet a cache-heavy 60-turn agent session costs $3.45 on Sonnet 5.5 and $2.55 on GPT-6.1 Sol, or $3.06 in the EU Data Zone that Claude still lacks. Above 272K input tokens the order flips, because GPT-6.1 Sol doubles its input rate while Sonnet 5.5 keeps flat pricing to 1M tokens and can run with no up-front reasoning.

Claude Opus 5.5 is GA in Microsoft Foundry at $4/$20 per million tokens with cache reads at $0.20, which cuts a cache-heavy 60-turn agent session from $8.63 on Opus 5 to $5.10 and brings it within 1.5x of Sonnet 5. The saving can reverse on uncached endpoints that ran Opus 5 with thinking disabled, because thinking is now always on, the default effort dropped to medium, and Foundry still offers no EU data zone, batch pricing or fast mode.

From 2 November 2026, new Microsoft 365 Copilot Business licences bought through CSP arrive with usage-based billing switched on, an Azure subscription attached, and Copilot Credits metering Cowork, the Work IQ APIs and GitHub Copilot Harness. Five settings in the Microsoft 365 admin center decide whether that becomes a budget line or a surprise invoice, and the defaults are not the ones a finance team would pick.

Microsoft AI published a draft Humanist AI Code of Conduct on 14 September 2026, committing its MAI models to absolute constraints on weapons, offensive cyber operations and resistance to shutdown, under a chain of command that operators and users cannot override. The scope line matters more than the constraints: the Code does not extend to third-party models Microsoft merely hosts, so GPT-5.6 in Microsoft 365 Copilot and Claude in Foundry sit outside it.

Valet mellan Azure och egen hårdvara för AI avgörs av tre faktorer: hur jämn er last är, vilka säkerhetskrav som faktiskt gäller er verksamhet och vilken driftkapacitet ni har. Vi går igenom kostnadsstrukturerna i båda spåren, brytpunkten där egen hårdvara blir billigare än betala-per-användning, vad Patientdatalagen och försvarsnära krav innebär i praktiken, och avslutar med en beslutsmatris och en checklista inför beslutet.

Claude Fable 5.1 keeps Fable 5's $10/$50 pricing but cuts cache reads to $0.25 per million tokens, which turns a 60-turn agent session from $17.25 into $10.50 and shrinks the premium over Opus 5 from 2x to about 22%. On Microsoft Foundry it ships Anthropic-hosted only, with no EU data zone, no Batches API, a zero default quota on pay-as-you-go, mandatory 30-day retention until Enterprise Frontier Safeguards arrive, and three breaking changes for teams migrating from Fable 5.

Moving Azure infrastructure from Terraform to Bicep is less about converting HCL files and more about replacing a state-file workflow with a deployment-based one. This field guide covers when migration pays off, inventorying tfstate, incremental coexistence patterns, the decompile tooling that exists, deployment stacks as the lifecycle answer, and the what-if validation and rollback discipline that keeps the cutover safe.

Anthropic prices prompt caching with three numbers: a 1.25x or 2x premium on cache writes depending on TTL, a 0.1x rate on cache reads, and the base input rate for everything after the last breakpoint. This deep-dive verifies every figure against the current official docs and covers per-model minimums, break-even math, batch stacking and how Claude on Azure converts it all into CCUs.

The Azure OpenAI Assistants API reached its retirement date on 26 August 2026, and the classic Foundry Agent Service it underpins retires 31 March 2027. A step-by-step migration guide to the new Foundry Agent Service on the Responses API: threads become conversations, runs become responses, assistants become versioned agents, and Microsoft's migration tool rewrites code but not stored state.

Next.js 16.3 shipped on 3 August 2026 with build disk caching on by default, up to 90% lower dev-server memory through eviction, TypeScript 7 type checking, and native Node.js streams that handle up to 22% more SSR requests under load. Here is what an Azure-hosted enterprise app gains from the upgrade, how to verify the wins in your own CI pipeline, and a decision guide for the opt-in Instant Navigations suite.

Microsoft's Agent Framework Harness and Foundry Hosted Agents reached general availability in early August 2026, wrapping models with function invocation, context compaction, planning, memory, tool approvals and OpenTelemetry in a runtime that runs locally, in containers, or consumption-billed on Foundry. A decision framework for Azure teams weighing the GA runtime against a hand-rolled agent loop, with cost levers and the Swedish compliance picture.

Sweden's AI Act enforcement map is now set: the SOU 2025:101 inquiry designates Post- och telestyrelsen (PTS) as coordinating market surveillance authority, with eleven surveillance bodies, two notifying authorities, and a PTS-run regulatory sandbox. The supplementary law was written to take effect on 2 August 2026 but awaits formal adoption, so PTS and its peers operate on interim government assignments while EU transparency rules already apply.

Regulation (EU) 2026/1744, the Digital Omnibus on AI, entered into force on 27 July 2026 and moves the AI Act deadline for Annex III high-risk systems from August 2026 to 2 December 2027, with Annex I embedded systems following in August 2028. Article 50 transparency still applies from 2 August 2026, a new prohibition arrives with a December 2026 marking deadline, and a phased 16-month plan turns the reprieve into a workable compliance programme.

Claude Opus 5 launched on 24 July 2026 at $5/$25 per million tokens with a 1M context window and day-one availability in Microsoft Foundry. For long-running agents the per-token price is the wrong unit: we work through cost per completed task against Sonnet 5 and GPT-5.6 Sol, and flag the EU data-residency caveat Swedish Azure teams need to check first.

Anthropic launched Claude Sonnet 5 on 30 June 2026 at an introductory 2/10 dollars per million tokens, posting 63.2% on SWE-bench Pro and near-Opus agentic performance at 40-60% of the cost per task. We run the cost math against Opus 4.8 and GPT-5.5, set out a routing framework for when the cheap model wins, and draw the continuity lesson from the eighteen-day Fable and Mythos export-control pause.

Claude Opus 4.8 and Claude Haiku 4.5 are now generally available in Microsoft Foundry, hosted on Azure with Entra ID authentication, prompt caching, extended thinking and billing through Claude Consumption Units on your existing Azure invoice. Deployment steps, the CCU cost model compared with Azure OpenAI, and the data-residency caveats Swedish and EU teams should assess before production use.

On 15 June 2026 IMY confirmed its role as market surveillance authority for the EU AI Act, with responsibility covering AI systems in areas such as law enforcement and credit assessment, alongside PTS and Finansinspektionen. For Swedish enterprises this puts GDPR and AI Act supervision under one regulator, and IMY's sandbox role offers a way to get data protection guidance before enforcement reaches full strength in 2027.

On 3 June 2026 the European Commission proposed the Cloud and AI Development Act, a regulation that introduces four Union assurance levels for cloud sovereignty and aims to at least triple EU data centre capacity within five to seven years. For Swedish public-sector and regulated teams on Azure, the framework will decide which workloads can stay on a US hyperscaler and which need an EU-controlled alternative, so the classification work should start now.

Microsoft Build 2026 turned Foundry into a full production-agent stack: Foundry IQ for unified retrieval, Toolboxes for managed tool access, agent memory, Voice Live and the experimental Scout Autopilot. Foundry IQ knowledge bases and Voice Live are generally available now, Toolboxes and memory sit in public preview, and Scout remains experimental, which sets the build, pilot and watch lanes for an Azure-first EU team.

Sweden's first national cloud policy (Fi2026/01233) bans no provider but makes jurisdictional exposure, portability and exit capability the questions every public-sector cloud decision must now answer in writing. For Azure estates, a defensible position means classified workloads, enforced Swedish and EU residency, customer-managed keys for sensitive data and a tested export path.

A practical pattern for rotating Azure secrets with zero downtime using Managed Identity, Key Vault rotation policies, and versioned references — including the common mistakes that cause rotation-induced outages.

A 2026 comparison of Bicep and Terraform for Azure — state management, provider coverage, drift detection, module ecosystems, team-scale considerations, and an honest recommendation matrix for different team shapes.

A grounded comparison of the three multi-tenant patterns on Azure — pool, silo, and bridge — on isolation, cost, blast radius, data sovereignty, and operational complexity. Plus concrete Prisma schema patterns for each.

Sweden Central is a three-zone region in Gävle whose AI model list now runs ahead of West Europe, but the choice that decides residency, model currency and cost is the Foundry deployment type rather than the region. This deep dive covers verified service and model availability, the EU Data Zone versus regional processing distinction, what data residency does and does not guarantee, DR pairing with restricted-access Sweden South, PTU capacity planning and list-price comparisons.

The honest cost model for self-hosted GitHub Actions runners on Azure — break-even math against hosted runners, when self-hosting is a trap, and the ephemeral scaleset architecture that keeps them safe in production.

Microsoft renamed Azure Cognitive Search to Azure AI Search in late 2023 and added substantial vector, semantic, and agentic-retrieval capabilities. Manufacturing teams running legacy Cognitive Search deployments need a structured migration plan — not a like-for-like upgrade, but a targeted modernisation of the features that matter most.