> [!note] Migrated issue > > <!--Drupal.org comment--> > > <!--Migrated from issue #3618011.--> > > Reported by: [joshua1234511](https://www.drupal.org/user/3362218) ### Problem/Motivation The last release was 1.1.0-beta4 on 24 June 2026. Since then both active branches have moved, and they have moved apart: * `1.1.x` is at `0af6c69b` (16 Aug 2026) with two unreleased commits: the `model_name` field plus its `update_10001()` hook, and the Project Update Bot's Drupal 12 compatibility change. * `1.2.x` is at `6f670fa5` (1 Sep 2026), carrying the `OpenAiBasedProviderClientBase` refactor from [#3552969](https://www.drupal.org/project/ai_provider_azure/issues/3552969). That refactor is a backwards-compatibility break, and it was developed against an older branch state, so 1.2.x is currently _missing_work that exists on 1.1.x — see [#3618009](https://www.drupal.org/project/ai_provider_azure/issues/3618009). **Drupal 12 is no longer a reason to release.** The AI Initiative's direction is that the `drupal/ai` 1.x line does not take Drupal 12; Drupal 12 support lands on `drupal/ai` 2.x, so Drupal 10 keeps working for as long as it has LTS. Azure follows its dependency, which makes the Azure 2.x line — the one that depends on `drupal/ai` 2.x — the branch that will carry Drupal 12. The branches currently say otherwise, and they cannot deliver what they say. Both `1.1.x` and `1.2.x` declare `core_version_requirement: ^10.3 || ^11 || ^12`, but `drupal/ai` 1.4.x declares `^10.5 || ^11.2` and `drupal/ai` 2.0.x declares `^11.2`. Neither allows Drupal 12. A site cannot install this module on Drupal 12 no matter what our `.info.yml` claims, so the claim is an unkeepable promise that we should not ship in a tag. (While that file is open: `1.2.x` requires `drupal/ai:^1.4.0`, which needs core `^10.5`, yet still advertises `^10.3`. Composer resolves to the stricter bound, but the declared floor is wrong and can be corrected in the same commit.) So the shape of the plan has changed. 1.1.0-beta5 was justified by getting Drupal 12 out to users; that justification is gone, and the release now exists to ship the `model_name` work and the translation and schema fixes, with the Drupal 12 claim taken back out first. 1.2.x still cannot be tagged without making an upgrade from 1.1.x a downgrade. This issue is the plan for getting both out, and a home for every open issue in the queue so nothing is left unplaced. ### Proposed resolution Two releases, in this order. **1. 1.1.0-beta5 — soon.** Deliberately small. Its job is to ship the `model_name` deployment-name split, which is the fix for the most-reported failure in this queue, and to correct the core requirement before it reaches a tag. **2. 1.2.0-beta1 — once 1.2.x has stopped regressing 1.1.x.** Headline is the refactor. Release notes must state the breaking changes: the three-argument `getClient()` was removed with no deprecation, `textToImage()` was rewritten, and `drupal/ai`moved from `^1.1.0` to `^1.4.0`. **Branch numbering — the open question from the original summary is now settled.** The 2.0.x name belongs to the `drupal/ai` 2.x line, which is [#3568475](https://www.drupal.org/project/ai_provider_azure/issues/3568475), and that line is where Drupal 12 will go. So 1.2.x stays 1.2.x and ships its existing break as a 1.x minor. [#3526346](https://www.drupal.org/project/ai_provider_azure/issues/3526346), which would break compatibility a second time, should wait for 2.0.x rather than stack another break onto 1.x. One caveat: `drupal/ai` 2.0.x does not declare `^12` yet either, so Azure 2.x can only follow once it does. ### Remaining tasks #### Blocking 1.1.0-beta5 * [#3617100](https://www.drupal.org/project/ai_provider_azure/issues/3617100) — **changed scope.** Revert the Project Update Bot's `|| ^12` on 1.1.x rather than closing it as done. Needs a merge request. * [#3592003](https://www.drupal.org/project/ai_provider_azure/issues/3592003) — merge [!30](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/30). Mergeable. The incorrect Dutch translation cannot be unpublished on localize.drupal.org until a release ships the fix. * [#3563730](https://www.drupal.org/project/ai_provider_azure/issues/3563730) — settings schema does not match stored config. A patch exists but no merge request; someone needs to raise one. * Tag 1.1.0-beta5. #### Blocking 1.2.0-beta1 * [#3618009](https://www.drupal.org/project/ai_provider_azure/issues/3618009) — port `model_name` and `ai_provider_azure.install` forward onto the refactored class. **The hard blocker**, and not a clean cherry-pick: 1.2.x has no `ai_provider_azure.install` at all, and `chat()` still sends `'model' => $model_id`. [!32](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/32) is open and now has an independent confirmation in comment #4 from a site running GPT-5.1 through Azure. * [#3594716](https://www.drupal.org/project/ai_provider_azure/issues/3594716) — **changed scope.** Same revert as #3617100, on 1.2.x. Needs a merge request. * [#3592003](https://www.drupal.org/project/ai_provider_azure/issues/3592003) — merge [!29](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/29), the 1.2.x side of the same fix. * [#3574913](https://www.drupal.org/project/ai_provider_azure/issues/3574913) — **verify before reviewing.** `response_format` is already absent from `text_to_image` in `definitions/api_defaults.yml` on both branches; the two remaining occurrences are audio and transcription. [!24](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/24) predates the refactor and may be moot. * [#3575634](https://www.drupal.org/project/ai_provider_azure/issues/3575634) — additional headers cause an error. [#3552969](https://www.drupal.org/project/ai_provider_azure/issues/3552969) explicitly lists this as not fixed, and `prepareClient()` is precisely where header handling moved. * [#3575716](https://www.drupal.org/project/ai_provider_azure/issues/3575716) — TTS returns "Resource not found". The reporter has already diagnosed it: `audio/speech` is appended to an endpoint that should not receive it. Azure Speech Service and Azure OpenAI TTS are different APIs. Needs a merge request. * Tag 1.2.0-beta1 with breaking changes documented. #### Newly reported — needs placing * [#3618012](https://www.drupal.org/project/ai_provider_azure/issues/3618012) — GPT-5.x rejects `max_tokens` and wants `max_completion_tokens`. This is ours to fix, on both branches: `max_tokens` is declared in `definitions/api_defaults.yml` and `chat()` merges the configuration straight into the payload, and `max_completion_tokens` appears nowhere in `drupal/ai` 1.4.x or 2.0.x, so it is not being handled upstream. It needs a decision on how the parameter is chosen — per-model configuration, or detection from the deployment — because the two names cannot both be sent. Worth considering for 1.1.0-beta5: the reporter is on 1.1.0-beta3, and newer deployments are the common case now. #### Close — the work is already done * [#3568629](https://www.drupal.org/project/ai_provider_azure/issues/3568629) — committed to 1.2.x as `6f670fa5` on 1 Sep 2026. Still open at RTBC; only the status is stale. #### Triage — open a long time with no maintainer response * [#3550566](https://www.drupal.org/project/ai_provider_azure/issues/3550566) — the reported error is "The API deployment for this resource does not exist", which is the exact problem the `model_name` deployment-name split addresses. Likely resolved by [#3618009](https://www.drupal.org/project/ai_provider_azure/issues/3618009); recheck and close or mark duplicate. * [#3581149](https://www.drupal.org/project/ai_provider_azure/issues/3581149) — most likely `minimum-stability` on the reporter's side rather than a packaging fault. Unanswered for five months. * [#3572773](https://www.drupal.org/project/ai_provider_azure/issues/3572773) — decide ownership. The route is ours, the `administer ai providers` permission belongs to the AI module. If the fix belongs there, move it rather than leaving it here. #### Merge request housekeeping * [!12](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/12) ([#3524559](https://www.drupal.org/project/ai_provider_azure/issues/3524559)) and [!3](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/3) ([#3484049](https://www.drupal.org/project/ai_provider_azure/issues/3484049)) both target `1.0.x`, which is unsupported. Retarget or close. !3 has been a draft since October 2024. #### After 1.2.0 — not in either release * [#3614660](https://www.drupal.org/project/ai_provider_azure/issues/3614660) — Responses API. [!33](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/33) is open against 1.2.x and at Needs review, further along than this plan first assumed, but it is still a cycle of work on its own and should not hold up 1.2.0-beta1. * [#3568475](https://www.drupal.org/project/ai_provider_azure/issues/3568475) — `drupal/ai` 2.x compatibility. This is the Azure 2.x line, and therefore the eventual home of Drupal 12 support. Stays postponed until the 2.x API settles. [!21](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/21) is already open. * [#3526346](https://www.drupal.org/project/ai_provider_azure/issues/3526346) — split `domain` and `api_path` out of `endpoint`. Needs a config update hook, so it is a breaking change; per the branch-numbering decision above, this belongs to 2.0.x. * [#3484049](https://www.drupal.org/project/ai_provider_azure/issues/3484049) — ImageAreaOfInterest. * [#3524559](https://www.drupal.org/project/ai_provider_azure/issues/3524559) — API key in additional headers. Postponed for maintainer information; pairs naturally with [#3575634](https://www.drupal.org/project/ai_provider_azure/issues/3575634). ### User interface changes None from this issue. The child issues carry their own; the only one of note is the **Model name** field restored by [#3618009](https://www.drupal.org/project/ai_provider_azure/issues/3618009). ### API changes None from this issue. 1.2.0-beta1 ships the breaks already made in [#3552969](https://www.drupal.org/project/ai_provider_azure/issues/3552969): three-argument `getClient()` removed without deprecation, `textToImage()` rewritten, and `drupal/ai` raised to `^1.4.0`. Both releases narrow `core_version_requirement` by removing `^12`, which is a correction rather than a regression, since the dependency never permitted Drupal 12. ### Data model changes None from this issue. [#3618009](https://www.drupal.org/project/ai_provider_azure/issues/3618009) reintroduces the `model_name` key under `ai.settings` with its update hook, and [#3526346](https://www.drupal.org/project/ai_provider_azure/issues/3526346) would later restructure the endpoint configuration.