Skip to content

Commit a802028

Browse files
authored
Merge pull request #286947 from MicrosoftDocs/main
9/18/2024 AM Publish
2 parents 0bc6b56 + 3588a5b commit a802028

21 files changed

+163
-212
lines changed

articles/application-gateway/for-containers/how-to-frontend-mtls-gateway-api.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: greglin
66
ms.service: azure-application-gateway
77
ms.subservice: appgw-for-containers
88
ms.topic: how-to
9-
ms.date: 9/17/2024
9+
ms.date: 9/18/2024
1010
ms.author: greglin
1111
---
1212

@@ -329,7 +329,8 @@ fqdn=$(kubectl get gateway gateway-01 -n test-infra -o jsonpath='{.status.addres
329329
Curling the FQDN of your frontend without the client certificate.
330330
331331
```bash
332-
curl --insecure https://$fqdn/```
332+
curl --insecure https://$fqdn/
333+
```
333334
334335
Note the response alerts a certificate is required.
335336

articles/automation/.openpublishing.redirection.automation.json

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -254,7 +254,17 @@
254254
"source_path_from_root": "/articles/automation/troubleshoot/start-stop-vm.md",
255255
"redirect_url": "/azure/azure-functions/start-stop-vms/troubleshoot",
256256
"redirect_document_id": false
257-
},
257+
},
258+
{
259+
"source_path_from_root": "/articles/automation/troubleshoot/automation-account.md",
260+
"redirect_url": "/azure/automation/enable-managed-identity-for-automation",
261+
"redirect_document_id": false
262+
},
263+
{
264+
"source_path_from_root": "/articles/automation/automation-managed-identity-faq.md",
265+
"redirect_url": "/azure/automation/enable-managed-identity-for-automation",
266+
"redirect_document_id": false
267+
},
258268
{
259269
"source_path_from_root": "/articles/automation/dsc-linux-powershell.md",
260270
"redirect_url": "/azure/automation/automation-dsc-overview",

articles/automation/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,6 +136,8 @@
136136
href: delete-account.md
137137
- name: Migrate from Orchestrator to Azure Automation (Beta)
138138
href: automation-orchestrator-migration.md
139+
- name: Context switching in Azure Automation
140+
href: context-switching.md
139141
- name: Shared resources
140142
items:
141143
- name: Manage certificates
@@ -278,6 +280,8 @@
278280
href: change-tracking/overview.md
279281
- name: Support regions for linked Log Analytics workspace
280282
href: how-to/region-mappings.md
283+
- name: Discover the software installed on your VMs
284+
href: automation-tutorial-installed-software.md
281285
- name: Enable
282286
items:
283287
- name: Enable from the Azure portal

articles/automation/automation-managed-identity-faq.md

Lines changed: 0 additions & 70 deletions
This file was deleted.

articles/automation/troubleshoot/automation-account.md

Lines changed: 0 additions & 73 deletions
This file was deleted.

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1228,7 +1228,7 @@ Allocation logic is similar to the [Microsoft.Targeting](#microsofttargeting) fe
12281228
12291229
### Overriding Enabled State with a Variant
12301230
1231-
You can use variants to override the enabled state of a feature flag. This gives variants an opportunity to extend the evaluation of a feature flag. If a caller is checking whether a flag that has variants is enabled, the feature manager will check if the variant assigned to the current user is set up to override the result. This is done using the optional variant property `status_override`. By default, this property is set to `None`, which means the variant doesn't affect whether the flag is considered enabled or disabled. Setting `status_override` to `Enabled` allows the variant, when chosen, to override a flag to be enabled. Setting `status_override` to `Disabled` provides the opposite functionality, therefore disabling the flag when the variant is chosen. A feature with an `enabled` state of `false` can't be overridden.
1231+
You can use variants to override the enabled state of a feature flag. This gives variants an opportunity to extend the evaluation of a feature flag. When calling `IsEnabled` on a flag with variants, the feature manager will check if the variant assigned to the current user is configured to override the result. This is done using the optional variant property `status_override`. By default, this property is set to `None`, which means the variant doesn't affect whether the flag is considered enabled or disabled. Setting `status_override` to `Enabled` allows the variant, when chosen, to override a flag to be enabled. Setting `status_override` to `Disabled` provides the opposite functionality, therefore disabling the flag when the variant is chosen. A feature with an `enabled` state of `false` can't be overridden.
12321232
12331233
If you're using a feature flag with binary variants, the `status_override` property can be very helpful. It allows you to continue using APIs like `IsEnabledAsync` and `FeatureGateAttribute` in your application, all while benefiting from the new features that come with variants, such as percentile allocation and seed.
12341234

@@ -1481,4 +1481,4 @@ To learn how to use feature filters, continue to the following tutorials.
14811481
To learn how to run experiments with variant feature flags, continue to the following tutorial.
14821482
14831483
> [!div class="nextstepaction"]
1484-
> [Run experiments with variant feature flags](./howto-feature-filters.md)
1484+
> [Run experiments with variant feature flags](./howto-feature-filters.md)

articles/azure-maps/map-add-heat-map-layer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,11 +107,11 @@ The `zoom` expression can only be used in `step` and `interpolate` expressions.
107107

108108
```json
109109
[
110-
`'interpolate',
110+
'interpolate',
111111
['exponential', 2],
112112
['zoom'],
113113
0, ['*', radiusMeters, 0.000012776039596366526],
114-
24, [`'*', radiusMeters, 214.34637593279402]
114+
24, ['*', radiusMeters, 214.34637593279402]
115115
]
116116
```
117117

articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,5 +35,10 @@
3535
"redirect_url": "/azure/azure-netapp-files/reservations",
3636
"redirect_document_id": false
3737
},
38+
{
39+
"source_path_from_root": "/articles/azure-netapp-files/optimize-costs-reserved-capacity.md",
40+
"redirect_url": "/azure/azure-netapp-files/reservations",
41+
"redirect_document_id": false
42+
}
3843
]
3944
}

articles/azure-netapp-files/backup-introduction.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 06/06/2024
8+
ms.date: 09/18/2024
99
ms.author: anfdocs
1010
ms.custom: references_regions
1111
---
@@ -49,6 +49,7 @@ Azure NetApp Files backup is supported for the following regions:
4949
* South Central US
5050
* South India
5151
* Southeast Asia
52+
* Spain Central
5253
* Sweden Central
5354
* Switzerland North
5455
* Switzerland West

articles/cost-management-billing/costs/tutorial-acm-create-budgets.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,8 +39,11 @@ In this tutorial, you learn how to:
3939
Budgets are supported for the following types of Azure account types and scopes:
4040

4141
- Azure role-based access control (Azure RBAC) scopes
42-
- Management groups
43-
- Subscription
42+
- Management group
43+
44+
- Subscription
45+
- Resource group
46+
4447
- Enterprise Agreement scopes
4548
- Billing account
4649
- Department

0 commit comments

Comments
 (0)