Skip to content

Commit ffc5294

Browse files
seesharprunseesharprun
authored
Merge branch 'MicrosoftDocs:main' into cosmos-retire-notebooks
2 parents f5c4c06 + e85ce60 commit ffc5294

File tree

52 files changed

+1021
-109
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

52 files changed

+1021
-109
lines changed

‎articles/ai-services/speech-service/how-to-pronunciation-assessment.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -91,23 +91,23 @@ In the `SpeechRecognizer`, you can specify the language to learn or practice imp
9191
::: zone pivot="programming-language-csharp"
9292

9393
```csharp
94-
var recognizer = new SpeechRecognizer(config, "en-US", audioInput);
94+
var recognizer = new SpeechRecognizer(speechConfig, "en-US", audioConfig);
9595
```
9696

9797
::: zone-end
9898

9999
::: zone pivot="programming-language-cpp"
100100

101101
```cpp
102-
auto recognizer = SpeechRecognizer::FromConfig(config, "en-US", audioConfig);
102+
auto recognizer = SpeechRecognizer::FromConfig(speechConfig, "en-US", audioConfig);
103103
```
104104

105105
::: zone-end
106106

107107
::: zone pivot="programming-language-java"
108108

109109
```Java
110-
SpeechRecognizer recognizer = new SpeechRecognizer(config, "en-US", audioInput);
110+
SpeechRecognizer recognizer = new SpeechRecognizer(speechConfig, "en-US", audioConfig);
111111
```
112112

113113
::: zone-end
@@ -131,15 +131,15 @@ speechConfig.speechRecognitionLanguage = "en-US";
131131
::: zone pivot="programming-language-objectivec"
132132

133133
```ObjectiveC
134-
SPXSpeechRecognizer* speechRecognizer = [[SPXSpeechRecognizer alloc] initWithSpeechConfiguration:speechConfig language:@"en-US" audioConfiguration:pronAudioSource];
134+
SPXSpeechRecognizer* recognizer = [[SPXSpeechRecognizer alloc] initWithSpeechConfiguration:speechConfig language:@"en-US" audioConfiguration:audioConfig];
135135
```
136136
137137
::: zone-end
138138
139139
::: zone pivot="programming-language-swift"
140140
141141
```swift
142-
let reco = try! SPXSpeechRecognizer(speechConfiguration: speechConfig, language: "en-US", audioConfiguration: audioInput)
142+
let recognizer = try! SPXSpeechRecognizer(speechConfiguration: speechConfig, language: "en-US", audioConfiguration: audioConfig)
143143
```
144144

145145
::: zone-end

‎articles/aks/azure-csi-blob-storage-provision.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ The following table includes parameters you can use to define a custom storage c
4747
|skuName | Specify an Azure storage account type (alias: `storageAccountType`). | `Standard_LRS`, `Premium_LRS`, `Standard_GRS`, `Standard_RAGRS` | No | `Standard_LRS`|
4848
|location | Specify an Azure location. | `eastus` | No | If empty, driver will use the same location name as current cluster.|
4949
|resourceGroup | Specify an Azure resource group name. | myResourceGroup | No | If empty, driver will use the same resource group name as current cluster.|
50-
|storageAccount | Specify an Azure storage account name.| storageAccountName | - No for blobfuse mount </br> - Yes for NFSv3 mount. | - For blobfuse mount: if empty, driver finds a suitable storage account that matches `skuName` in the same resource group. If a storage account name is provided, storage account must exist. </br> - For NFSv3 mount, storage account name must be provided.|
50+
|storageAccount | Specify an Azure storage account name.| storageAccountName | - No | When a specific storage account name is not provided, the driver will look for a suitable storage account that matches the account settings within the same resource group. If it fails to find a matching storage account, it will create a new one. However, if a storage account name is specified, the storage account must already exist. |
5151
|networkEndpointType| Specify network endpoint type for the storage account created by driver. If privateEndpoint is specified, a [private endpoint][storage-account-private-endpoint] is created for the storage account. For other cases, a service endpoint will be created for NFS protocol.<sup>1</sup> | `privateEndpoint` | No | For an AKS cluster, add the AKS cluster name to the Contributor role in the resource group hosting the VNET.|
5252
|protocol | Specify blobfuse mount or NFSv3 mount. | `fuse`, `nfs` | No | `fuse`|
5353
|containerName | Specify the existing container (directory) name. | container | No | If empty, driver creates a new container name, starting with `pvc-fuse` for blobfuse or `pvc-nfs` for NFS v3. |

‎articles/aks/azure-csi-files-storage-provision.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to create a static or dynamic persistent volume with Azur
55
ms.topic: article
66
ms.custom: devx-track-azurecli
77
ms.subservice: aks-storage
8-
ms.date: 06/28/2024
8+
ms.date: 07/09/2024
99
author: tamram
1010
ms.author: tamram
1111

@@ -57,6 +57,7 @@ The following table includes parameters you can use to define a custom storage c
5757
|shareName | Specify Azure file share name. | Existing or new Azure file share name. | No | If empty, driver generates an Azure file share name. |
5858
|shareNamePrefix | Specify Azure file share name prefix created by driver. | Share name can only contain lowercase letters, numbers, hyphens, and length should be fewer than 21 characters. | No |
5959
|skuName | Azure Files storage account type (alias: `storageAccountType`)| `Standard_LRS`, `Standard_ZRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_RAGZRS`,`Premium_LRS`, `Premium_ZRS` | No | `StandardSSD_LRS`<br> Minimum file share size for Premium account type is 100 GB.<br> ZRS account type is supported in limited regions.<br> NFS file share only supports Premium account type.|
60+
|storageAccount | Specify an Azure storage account name.| storageAccountName | - No | When a specific storage account name is not provided, the driver will look for a suitable storage account that matches the account settings within the same resource group. If it fails to find a matching storage account, it will create a new one. However, if a storage account name is specified, the storage account must already exist. |
6061
|storageEndpointSuffix | Specify Azure storage endpoint suffix. | `core.windows.net`, `core.chinacloudapi.cn`, etc. | No | If empty, driver uses default storage endpoint suffix according to cloud environment. For example, `core.windows.net`. |
6162
|tags | [Tags][tag-resources] are created in new storage account. | Tag format: 'foo=aaa,bar=bbb' | No | "" |
6263
|--- | **Following parameters are only for SMB protocol** | --- | --- |

‎articles/aks/long-term-support.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,8 @@ To carry out an in-place upgrade to the latest LTS version, you need to specify
128128
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.32.2
129129
```
130130
> [!NOTE]
131-
> The next Long Term Support Version after 1.27 is to be determined. However Customers will get a minimum 6 months of overlap between 1.27 LTS and the next LTS version to plan upgrades.
131+
132+
> 1.30 is the next LTS version after 1.27. Customers will be able to upgrade from 1.27 LTS to 1.30 LTS starting August, 2024. 1.27 LTS goes End of Life by July 2025.
132133
> Kubernetes 1.32.2 is used as an example version in this article. Check the [AKS release tracker](release-tracker.md) for available Kubernetes releases.
133134
134135
## Frequently asked questions

‎articles/azure-app-configuration/concept-feature-management.md

Lines changed: 38 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -74,19 +74,44 @@ To use feature flags effectively, you need to externalize all the feature flags
7474

7575
Azure App Configuration provides a centralized repository for feature flags. You can use it to define different kinds of feature flags and manipulate their states quickly and confidently. You can then use the App Configuration libraries for various programming language frameworks to easily access these feature flags from your application.
7676

77-
[The feature flags in an ASP.NET Core app](./use-feature-flags-dotnet-core.md) shows how the App Configuration .NET provider and Feature Management libraries are used together to implement feature flags for your ASP.NET web application. For more information on feature flags in Azure App Configuration, see the following articles:
78-
79-
* [Manage feature flags](./manage-feature-flags.md)
80-
* [Use conditional feature flags](./howto-feature-filters-aspnet-core.md)
81-
* [Enable a feature for specified users/groups](./howto-targetingfilter-aspnet-core.md)
82-
* [Add feature flags to an ASP.NET Core app](./quickstart-feature-flag-aspnet-core.md)
83-
* [Add feature flags to a .NET Framework app](./quickstart-feature-flag-dotnet.md)
84-
* [Add feature flags to an Azure Functions app](./quickstart-feature-flag-azure-functions-csharp.md)
85-
* [Add feature flags to a Spring Boot app](./quickstart-feature-flag-spring-boot.md)
86-
* [Use feature flags in an ASP.NET Core](./use-feature-flags-dotnet-core.md)
87-
* [Use feature flags in a Spring Boot app](./use-feature-flags-spring-boot.md)
88-
8977
## Next steps
9078

79+
To start using feature flags with Azure App Configuration, continue to the following quickstarts specific to your application’s language or platform.
80+
81+
> [!div class="nextstepaction"]
82+
> [ASP.NET Core](./quickstart-feature-flag-aspnet-core.md)
83+
9184
> [!div class="nextstepaction"]
92-
> [Add feature flags to an ASP.NET Core web app](./quickstart-feature-flag-aspnet-core.md)
85+
> [.NET/.NET Framework](./quickstart-feature-flag-dotnet.md)
86+
87+
> [!div class="nextstepaction"]
88+
> [.NET background service](./quickstart-feature-flag-dotnet-background-service.md)
89+
90+
> [!div class="nextstepaction"]
91+
> [Java Spring](./quickstart-feature-flag-spring-boot.md)
92+
93+
> [!div class="nextstepaction"]
94+
> [Python](./quickstart-feature-flag-python.md)
95+
96+
> [!div class="nextstepaction"]
97+
> [Azure Kubernetes Service](./quickstart-feature-flag-azure-kubernetes-service.md)
98+
99+
> [!div class="nextstepaction"]
100+
> [Azure Functions](./quickstart-feature-flag-azure-functions-csharp.md)
101+
102+
To learn more about managing feature flags in Azure App Configuration, continue to the following tutorial.
103+
104+
> [!div class="nextstepaction"]
105+
> [Manage feature flags in Azure App Configuration](./manage-feature-flags.md)
106+
107+
Feature filters allow you to enable a feature flag conditionally. Azure App Configuration offers built-in feature filters that enable you to activate a feature flag only during a specific period or to a particular targeted audience of your app. For more information, continue to the following tutorial.
108+
109+
> [!div class="nextstepaction"]
110+
> [Enable conditional features with feature filters](./howto-feature-filters.md)
111+
112+
> [!div class="nextstepaction"]
113+
> [Enable features on a schedule](./howto-timewindow-filter.md)
114+
115+
> [!div class="nextstepaction"]
116+
> [Roll out features to targeted audiences](./howto-targetingfilter.md)
117+

‎articles/azure-app-configuration/feature-management-dotnet-reference.md

Lines changed: 38 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,17 @@
11
---
2-
title: .NET feature management - Azure App Configuration
3-
description: Overview of .NET Feature Management library
2+
title: .NET feature flag management
3+
titleSuffix: Azure App Configuration
4+
description: In this tutorial, you learn how to use feature flags in .NET apps. The feature management library provides various out-of-the-box solutions for application development, ranging from simple feature toggles to complex feature experimentation.
45
services: azure-app-configuration
56
author: zhiyuanliang-ms
67
ms.author: zhiyuanliang
78
ms.service: azure-app-configuration
9+
ms.devlang: csharp
810
ms.custom: devx-track-dotnet
911
ms.topic: tutorial
1012
ms.date: 05/22/2024
1113
zone_pivot_groups: feature-management
14+
#Customer intent: I want to control feature availability in my app by using the Feature Management library.
1215
---
1316

1417
# .NET Feature Management
@@ -323,10 +326,10 @@ By default, the feature manager retrieves feature flag configuration from the "F
323326

324327
> [!NOTE]
325328
> You can also specify that feature flag configuration should be retrieved from a different configuration section by passing the section to `AddFeatureManagement`. The following example tells the feature manager to read from a different section called "MyFeatureFlags" instead:
326-
327-
``` C#
328-
services.AddFeatureManagement(configuration.GetSection("MyFeatureFlags"));
329-
```
329+
>
330+
> ``` C#
331+
> services.AddFeatureManagement(configuration.GetSection("MyFeatureFlags"));
332+
> ```
330333
331334
### Dependency Injection
332335
@@ -1423,3 +1426,32 @@ To use an implementation of `IFeatureDefinitionProvider`, it must be added into
14231426
services.AddSingleton<IFeatureDefinitionProvider, InMemoryFeatureDefinitionProvider>()
14241427
.AddFeatureManagement()
14251428
```
1429+
1430+
## Next steps
1431+
1432+
To learn how to use feature flags in your applications, continue to the following quickstarts.
1433+
1434+
> [!div class="nextstepaction"]
1435+
> [ASP.NET Core](./quickstart-feature-flag-aspnet-core.md)
1436+
1437+
> [!div class="nextstepaction"]
1438+
> [.NET/.NET Framework console app](./quickstart-feature-flag-dotnet.md)
1439+
1440+
> [!div class="nextstepaction"]
1441+
> [.NET background service](./quickstart-feature-flag-dotnet-background-service.md)
1442+
1443+
To learn how to use feature filters, continue to the following tutorials.
1444+
1445+
> [!div class="nextstepaction"]
1446+
> [Enable conditional features with feature filters](./howto-feature-filters.md)
1447+
1448+
> [!div class="nextstepaction"]
1449+
> [Enable features on a schedule](./howto-timewindow-filter.md)
1450+
1451+
> [!div class="nextstepaction"]
1452+
> [Roll out features to targeted audiences](./howto-targetingfilter.md)
1453+
1454+
To learn how to run experiments with variant feature flags, continue to the following tutorial.
1455+
1456+
> [!div class="nextstepaction"]
1457+
> [Run experiments with variant feature flags](./howto-feature-filters.md)

‎articles/azure-app-configuration/howto-feature-filters-aspnet-core.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,3 +94,8 @@ To learn more about the built-in feature filters, continue to the following tuto
9494

9595
> [!div class="nextstepaction"]
9696
> [Roll out features to targeted audience](./howto-targetingfilter.md)
97+
98+
For the full feature rundown of the .NET feature management library, continue to the following document.
99+
100+
> [!div class="nextstepaction"]
101+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/howto-targetingfilter-aspnet-core.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -228,3 +228,8 @@ To learn more about the feature filters, continue to the following tutorials.
228228
229229
> [!div class="nextstepaction"]
230230
> [Enable features on a schedule](./howto-timewindow-filter-aspnet-core.md)
231+
232+
For the full feature rundown of the .NET feature management library, continue to the following document.
233+
234+
> [!div class="nextstepaction"]
235+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/howto-timewindow-filter-aspnet-core.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,3 +58,8 @@ To learn more about the feature filters, continue to the following tutorials.
5858
5959
> [!div class="nextstepaction"]
6060
> [Roll out features to targeted audience](./howto-targetingfilter.md)
61+
62+
For the full feature rundown of the .NET feature management library, continue to the following document.
63+
64+
> [!div class="nextstepaction"]
65+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/manage-feature-flags.md

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Use Azure App Configuration to manage feature flags"
2+
title: Use Azure App Configuration to manage feature flags
33
titleSuffix: Azure App Configuration
44
description: In this quickstart, you learn how to manage feature flags separately from your application by using Azure App Configuration.
55
services: azure-app-configuration
@@ -143,5 +143,25 @@ Feature flags created with the Feature manager are stored as regular key-values.
143143

144144
## Next steps
145145

146+
To start using feature flags with Azure App Configuration, continue to the following quickstarts specific to your application’s language or platform.
147+
148+
> [!div class="nextstepaction"]
149+
> [ASP.NET Core](./quickstart-feature-flag-aspnet-core.md)
150+
151+
> [!div class="nextstepaction"]
152+
> [.NET/.NET Framework](./quickstart-feature-flag-dotnet.md)
153+
154+
> [!div class="nextstepaction"]
155+
> [.NET background service](./quickstart-feature-flag-dotnet-background-service.md)
156+
157+
> [!div class="nextstepaction"]
158+
> [Java Spring](./quickstart-feature-flag-spring-boot.md)
159+
160+
> [!div class="nextstepaction"]
161+
> [Python](./quickstart-feature-flag-python.md)
162+
163+
> [!div class="nextstepaction"]
164+
> [Azure Kubernetes Service](./quickstart-feature-flag-azure-kubernetes-service.md)
165+
146166
> [!div class="nextstepaction"]
147-
> [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md)
167+
> [Azure Functions](./quickstart-feature-flag-azure-functions-csharp.md)

0 commit comments

Comments
 (0)