Skip to content

Commit 6f403b2

Browse files
authored
Merge pull request #286848 from MicrosoftDocs/main
Publish to live, Tuesday 4 AM PST, 9/17
2 parents 8b4c6d4 + 64163af commit 6f403b2

File tree

49 files changed

+3083
-1267
lines changed

Some content is hidden

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

49 files changed

+3083
-1267
lines changed

articles/api-management/authentication-basic-policy.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ ms.author: danlep
1616

1717
Use the `authentication-basic` policy to authenticate with a backend service using Basic authentication. This policy effectively sets the HTTP Authorization header to the value corresponding to the credentials provided in the policy.
1818

19+
[!INCLUDE [api-management-credentials-caution](../../includes/api-management-credentials-caution.md)]
20+
1921
[!INCLUDE [api-management-policy-generic-alert](../../includes/api-management-policy-generic-alert.md)]
2022

2123

articles/api-management/authentication-certificate-policy.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ ms.author: danlep
1414

1515
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1616

17-
Use the `authentication-certificate` policy to authenticate with a backend service using a client certificate. When the certificate is [installed into API Management](./api-management-howto-mutual-certificates.md) first, identify it first by its thumbprint or certificate ID (resource name).
17+
Use the `authentication-certificate` policy to authenticate with a backend service using a client certificate. When the certificate is [installed into API Management](./api-management-howto-mutual-certificates.md) first, identify it first by its thumbprint or certificate ID (resourcename).
18+
19+
[!INCLUDE [api-management-credentials-caution](../../includes/api-management-credentials-caution.md)]
1820

1921
> [!CAUTION]
2022
> If the certificate references a certificate stored in Azure Key Vault, identify it using the certificate ID. When a key vault certificate is rotated, its thumbprint in API Management will change, and the policy will not resolve the new certificate if it is identified by thumbprint.
@@ -43,6 +45,12 @@ ms.author: danlep
4345
- [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
4446
- [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted, workspace
4547

48+
### Usage notes
49+
50+
- We recommend configuring [key vault certificates](api-management-howto-mutual-certificates.md) to manage certificates used to secure access to backend services.
51+
- If you configure a certificate password in this policy, we recommend using a [named value](api-management-howto-properties.md).
52+
53+
4654
## Examples
4755

4856
### Client certificate identified by the certificate ID

articles/api-management/proxy-policy.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ ms.author: danlep
1616

1717
The `proxy` policy allows you to route requests forwarded to backends via an HTTP proxy. Only HTTP (not HTTPS) is supported between the gateway and the proxy. Basic and NTLM authentication only.
1818

19+
[!INCLUDE [api-management-credentials-caution](../../includes/api-management-credentials-caution.md)]
20+
1921
[!INCLUDE [api-management-policy-generic-alert](../../includes/api-management-policy-generic-alert.md)]
2022

2123

@@ -39,6 +41,11 @@ The `proxy` policy allows you to route requests forwarded to backends via an HTT
3941
- [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
4042
- [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted, workspace
4143

44+
### Usage notes
45+
46+
- We recommend using [named values](api-management-howto-properties.md) to provide credentials, with secrets protected in a key vault.
47+
48+
4249
## Example
4350

4451
In this example, [named values](api-management-howto-properties.md) are used for the username and password to avoid storing sensitive information in the policy document.

articles/api-management/virtual-network-workspaces-resources.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,11 @@ For information about networking options in API Management, see [Use a virtual n
3131

3232
* The subnet can't be shared with another Azure resource, including another workspace gateway.
3333

34+
## Subnet size
35+
36+
* Minimum: /27 (32 addresses)
37+
* Maximum: /24 (256 addresses) - recommended
38+
3439
## Subnet delegation
3540

3641
The subnet must be delegated as follows to enable the desired inbound and outbound access.

articles/azure-boost/includes/azure-boost-series.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ ms.custom:
1313

1414
| Size Series | Series Type | Deployment Status |
1515
|:-:|:-:|:-:|
16-
|[Msv3/Mdsv3](/azure/virtual-machines/msv3-mdsv3-medium-series)| Medium Memory | Production |
17-
|[Mbsv3/Mbdsv3](/azure/virtual-machines/sizes/memory-optimized/mbsv3-mbdsv3-series)| Medium Memory| Preview|
18-
|Msv3/Mdsv3| High Memory | Preview|
19-
|Msv3/Mdsv3| Very High Memory | Preview|
16+
| [Msv3/Mdsv3](/azure/virtual-machines/msv3-mdsv3-medium-series)| Medium Memory | Production |
17+
| [Mbsv3/Mbdsv3](/azure/virtual-machines/sizes/memory-optimized/mbsv3-mbdsv3-series)| Medium Memory| Preview|
18+
| Msv3/Mdsv3| High Memory | Preview|
19+
| Msv3/Mdsv3| Very High Memory | Preview|
2020
| [Dlsv6/Dldsv6](/azure/virtual-machines/dlsv6-dldsv6-series) | General Purpose | Preview |
2121
| [Dsv6/Ddsv6](/azure/virtual-machines/dsv6-ddsv6-series) | General Purpose | Preview |
2222
| [Esv6/Edsv6](/azure/virtual-machines/esv6-edsv6-series) | Memory Optimized | Preview |
@@ -27,7 +27,9 @@ ms.custom:
2727
| [ECesv5](/azure/virtual-machines/ecesv5-ecedsv5-series) | Memory Optimized | Preview |
2828
| [Mv3 Medium Memory](/azure/virtual-machines/msv3-mdsv3-medium-series)| High Memory to CPU Optimized | Production |
2929
| [Falsv6/Famsv6](/azure/virtual-machines/fasv6-falsv6-series) | Compute Optimized | Preview |
30-
| [Dlsv5](/azure/virtual-machines/dlsv5-dldsv5-series) | General Purpose | Production |
30+
| [Dlsv5/Dldsv5](/azure/virtual-machines/dlsv5-dldsv5-series) | General Purpose | Production |
31+
| [Ddsv5](/azure/virtual-machines/sizes/general-purpose/ddsv5-series)| General Purpose | Production |
32+
| [Ddv5](/azure/virtual-machines/sizes/general-purpose/ddv5-series)| General Purpose | Production |
3133
| [Dv5/Dsv5](/azure/virtual-machines/dv5-dsv5-series) | General Purpose | Production |
3234
| [Ev5/Esv5](/azure/virtual-machines/ev5-esv5-series) | Memory Optimized | Production |
3335
| [Ebsv5](/azure/virtual-machines/ebdsv5-ebsv5-series) | Managed disks optimized | Production |

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,11 @@
2929
"source_path_from_root": "/articles/azure-netapp-files/backup-disable.md",
3030
"redirect_url": "/azure/azure-netapp-files/backup-configure-manual",
3131
"redirect_document_id": false
32+
},
33+
{
34+
"source_path_from_root": "/articles/azure-netapp-files/reserved-capacity.md",
35+
"redirect_url": "/azure/azure-netapp-files/whats-new",
36+
"redirect_document_id": false
3237
}
3338
]
3439
}

articles/azure-netapp-files/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,6 @@
8787
href: azure-netapp-files-cost-model.md
8888
- name: Azure NetApp Files storage with cool access
8989
href: cool-access-introduction.md
90-
- name: Azure NetApp Files reserved capacity
91-
href: reserved-capacity.md
9290
- name: Quotas
9391
items:
9492
- name: Understand volume quota

articles/azure-netapp-files/reserved-capacity.md

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

articles/azure-netapp-files/whats-new.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,22 +6,14 @@ author: b-hchen
66
ms.service: azure-netapp-files
77
ms.custom: linux-related-content
88
ms.topic: overview
9-
ms.date: 09/16/2024
9+
ms.date: 08/20/2024
1010
ms.author: anfdocs
1111
---
1212

1313
# What's new in Azure NetApp Files
1414

1515
Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
1616

17-
## September 2024
18-
19-
* [Reserved capacity](reserved-capacity.md) is now generally available (GA)
20-
21-
Pay-as-you-go pricing is the most convenient way to purchase cloud storage when your workloads are dynamic or changing over time. However, some workloads are more predictable with stable capacity usage over an extended period. These workloads can benefit from savings in exchange for a longer-term commitment. With a one-year or three-year commitment of Azure NetApp Files reserved capacity, you can save up to 34% on sustained usage of Azure NetApp Files. Reserved capacity is available in stackable increments of 100 TiB and 1 PiB on Standard, Premium and Ultra service levels in a given region. Reserved capacity can be used in a single subscription (single-subscription scope), or across multiple subscriptions (shared scope) in the same Azure tenant. Azure NetApp Files reserved capacity benefits are automatically applied to existing Azure NetApp Files capacity pools in the matching region and service level. Azure NetApp Files reserved capacity not only provides cost savings but also improves financial predictability and stability, allowing for more effective budgeting. Additional usage is conveniently billed at the regular pay-as-you-go rate.
22-
23-
For more detail, see the [Azure NetApp Files reserved capacity](reserved-capacity.md) or see reservations in the Azure portal.
24-
2517
## August 2024
2618

2719
* [Azure NetApp Files storage with cool access](cool-access-introduction.md) is now generally available (GA) and supported with the Standard, Premium, and Ultra service levels. Cool access is also now supported for destination volumes in cross-region/cross-zone relationships.

articles/communication-services/how-tos/calling-sdk/includes/call-context/call-context-web.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ ms.date: 09/13/2024
66
ms.author: micahvivion
77
---
88

9+
910
## Technical parameters
1011
The calling SDK supports adding up to 5 custom SIP headers and 1000 custom VOIP headers. Additionally, developers can include a dedicated User-To-User header as part of SIP headers list.
1112

@@ -20,6 +21,7 @@ When adding these custom headers as a developer you can choose to add only SIP h
2021
> [!NOTE]
2122
> Currently, adding custom User-to-User Information headers is only supported when initiating a 1:1 call. Passing User-to-User Information headers in group calls is not currently supported. To work around this after starting the 1:1 call, you can include additional participants while maintaining the User-to-User Information within the calls.
2223
24+
For details othe custom context interface API, consult the [custom context API resource](/javascript/api/azure-communication-services/@azure/communication-calling/customcontext?view=azure-communication-services-js&preserve-view=true) page.
2325

2426
## Place a call with User-to-User Information (UUI) data
2527

0 commit comments

Comments
 (0)