Skip to content

Commit fb5e240

Browse files
Merge pull request #7210 from goergenj/byos-gating-removal
BYOS remove gating requirement instructions
2 parents 33ded2a + 47aeec6 commit fb5e240

File tree

1 file changed

+8
-98
lines changed

1 file changed

+8
-98
lines changed

articles/ai-services/speech-service/bring-your-own-storage-speech-resource.md

Lines changed: 8 additions & 98 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,11 @@ manager: nitinme
66
ms.service: azure-ai-speech
77
ms.custom: devx-track-azurepowershell
88
ms.topic: how-to
9-
ms.date: 08/07/2025
10-
author: PatrickFarley
11-
ms.author: pafarley
12-
ms.reviewer: jagoerge
9+
ms.date: 09/22/2025
10+
author: goergenj
11+
reviewer: PatrickFarley
12+
ms.author: jagoerge
13+
ms.reviewer: pafarley
1314
---
1415

1516
# Set up the Bring your own storage (BYOS) Speech resource
@@ -22,6 +23,9 @@ There's one exception: if you use Text to speech, and your Speech resource and t
2223

2324
BYOS can be used with several Azure AI services. For Speech, it can be used in the following scenarios:
2425

26+
> [!NOTE]
27+
> Speech services BYOS is currently only supported with resource kind `SpeechServices`.
28+
2529
**Speech to text**
2630

2731
- [Batch transcription](batch-transcription.md)
@@ -51,98 +55,6 @@ Consider the following rules when planning BYOS-enabled Speech resource configur
5155

5256
This section describes how to create a BYOS enabled Speech resource.
5357

54-
55-
### Request access to BYOS for your Azure subscriptions
56-
57-
You need to request access to BYOS functionality for each of the Azure subscriptions you plan to use. To request access, fill and submit [Cognitive Services & Applied AI Customer Managed Keys and Bring Your Own Storage access request form](https://aka.ms/cogsvc-cmk). Wait for the request to be approved.
58-
59-
### (Optional) Check whether Azure subscription has access to BYOS
60-
61-
You can quickly check whether your Azure subscription has access to BYOS. This check uses [preview features](/azure/azure-resource-manager/management/preview-features) functionality of Azure.
62-
63-
# [Azure portal](#tab/portal)
64-
65-
This functionality isn't available through Azure portal.
66-
67-
> [!NOTE]
68-
> You may view the list of preview features for a given Azure subscription as explained in [this article](/azure/azure-resource-manager/management/preview-features), however note that not all preview features, including BYOS are visible this way.
69-
70-
# [PowerShell](#tab/powershell)
71-
72-
To check whether an Azure subscription has access to BYOS with PowerShell, we use [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) command.
73-
74-
You can [install PowerShell locally](/powershell/azure/install-azure-powershell) or use [Azure Cloud Shell](/azure/cloud-shell/overview).
75-
76-
If you use local installation of PowerShell, connect to your Azure account using `Connect-AzAccount` command before trying the following script.
77-
78-
```azurepowershell
79-
# Target subscription parameters
80-
# REPLACE WITH YOUR CONFIGURATION VALUES
81-
$azureSubscriptionId = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
82-
83-
# Select the right subscription
84-
Set-AzContext -SubscriptionId $azureSubscriptionId
85-
86-
# Check whether the Azure subscription has access to BYOS
87-
Get-AzProviderFeature -ListAvailable -ProviderNamespace "Microsoft.CognitiveServices" | where-object FeatureName -Match byox
88-
```
89-
90-
If you get the response like this, your subscription has access to BYOS.
91-
```powershell
92-
FeatureName ProviderName RegistrationState
93-
----------- ------------ -----------------
94-
byoxPreview Microsoft.CognitiveServices Registered
95-
```
96-
97-
If you get empty response or `RegistrationState` value is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
98-
99-
# [Azure CLI](#tab/azure-cli)
100-
101-
To check whether an Azure subscription has access to BYOS with Azure CLI, we use [az feature show](/cli/azure/feature) command.
102-
103-
You can [install Azure CLI locally](/cli/azure/install-azure-cli) or use [Azure Cloud Shell](/azure/cloud-shell/overview).
104-
105-
> [!NOTE]
106-
> The following script doesn't use variables because variable usage differs, depending on the platform where Azure CLI runs. See information on Azure CLI variable usage in [this article](/cli/azure/azure-cli-variables).
107-
108-
If you use local installation of Azure CLI, connect to your Azure account using `az login` command before trying the following script.
109-
110-
```azurecli
111-
az account set --subscription "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
112-
113-
az feature show --name byoxPreview --namespace Microsoft.CognitiveServices --output table
114-
```
115-
116-
If you get the response like this, your subscription has access to BYOS.
117-
```dos
118-
Name RegistrationState
119-
--------------------------------------- -------------------
120-
Microsoft.CognitiveServices/byoxPreview Registered
121-
```
122-
If you get empty response or `RegistrationState` value is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
123-
124-
> [!Tip]
125-
> See additional commands related to listing Azure subscription preview features in [this article](/azure/azure-resource-manager/management/preview-features).
126-
127-
# [REST](#tab/rest)
128-
129-
To check through REST API whether an Azure subscription has access to BYOS use [Features - List](/rest/api/resources/features/list) request from Azure Resource Manager REST API.
130-
131-
If your subscription has access to BYOS, the REST response will contain the following element:
132-
```json
133-
{
134-
"properties": {
135-
"state": "Registered"
136-
},
137-
"id": "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/providers/Microsoft.Features/providers/Microsoft.CognitiveServices/features/byoxPreview",
138-
"type": "Microsoft.Features/providers/features",
139-
"name": "Microsoft.CognitiveServices/byoxPreview"
140-
}
141-
```
142-
If the REST response doesn't contain the reference to `byoxPreview` feature or its state is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
143-
***
144-
145-
14658
### Plan and prepare your Storage account
14759

14860
If you use Azure portal to create a BYOS-enabled Speech resource, an associated Storage account can be created automatically. For all other provisioning methods (Azure CLI, PowerShell, REST API Request) you need to use existing Storage account.
@@ -157,8 +69,6 @@ If you want to use existing Storage account and don't intend to use Azure portal
15769
15870
### Create BYOS-enabled Speech resource
15971

160-
Make sure your Azure subscription is enabled for using BYOS before attempting to create the Speech resource. See [this section](#request-access-to-byos-for-your-azure-subscriptions).
161-
16272
There are two ways of creating a BYOS-enabled Speech resource:
16373

16474
- With Azure portal.

0 commit comments

Comments
 (0)