Skip to content

Commit 20e685d

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sarat-toc
2 parents 6546ea1 + 8ef8a57 commit 20e685d

File tree

13 files changed

+61
-121
lines changed

13 files changed

+61
-121
lines changed

articles/api-management/api-management-howto-aad-b2c.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Azure Active Directory B2C is a cloud identity management solution for consumer-
1919
In this tutorial, you'll learn the configuration required in your API Management service to integrate with Azure Active Directory B2C. As noted later in this article, if you are using the deprecated legacy developer portal, some steps will differ.
2020

2121
> [!IMPORTANT]
22-
> * This article has been updated with steps to configure an Azure AD B2C app using the Microsoft Authentication Library ([MSAL](../active-directory/develop/msal-overview.md)) v2.0.
22+
> * This article has been updated with steps to configure an Azure AD B2C app using the Microsoft Authentication Library ([MSAL](../active-directory/develop/msal-overview.md)).
2323
> * If you previously configured an Azure AD B2C app for user sign-in using the Azure AD Authentication Library (ADAL), we recommend that you [migrate to MSAL](#migrate-to-msal).
2424
2525
For information about enabling access to the developer portal by using classic Azure Active Directory, see [How to authorize developer accounts using Azure Active Directory](api-management-howto-aad.md).

articles/azure-arc/data/toc.yml

Lines changed: 0 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -116,72 +116,6 @@ items:
116116
href: troubleshoot-guide.md
117117
- name: Get logs
118118
href: troubleshooting-get-logs.md
119-
- name: Azure Arc-enabled PostgreSQL Hyperscale (preview)
120-
items:
121-
- name: Overview
122-
items:
123-
- name: What is Azure Arc-enabled PostgreSQL Hyperscale
124-
href: what-is-azure-arc-enabled-postgres-hyperscale.md
125-
- name: Limitations
126-
href: limitations-postgresql-hyperscale.md
127-
- name: Quickstarts
128-
items:
129-
- name: Supported versions
130-
href: supported-versions-postgres-hyperscale.md
131-
- name: Create PostgreSQL Hyperscale server group (CLI)
132-
href: create-postgresql-hyperscale-server-group.md
133-
- name: Create PostgreSQL Hyperscale server group (portal)
134-
href: create-postgresql-hyperscale-server-group-azure-portal.md
135-
- name: Create PostgreSQL Hyperscale server group (Azure Data Studio)
136-
href: create-postgresql-hyperscale-server-group-azure-data-studio.md
137-
- name: Create PostgreSQL Hyperscale server group - Kubernetes native tools
138-
href: create-postgresql-hyperscale-server-group-kubernetes-native-tools.md
139-
- name: Connect
140-
href: get-connection-endpoints-and-connection-strings-postgres-hyperscale.md
141-
- name: Concepts
142-
items:
143-
- name: Distribute data
144-
href: concepts-distributed-postgres-hyperscale.md
145-
- name: Server group placement
146-
href: postgresql-hyperscale-server-group-placement-on-kubernetes-cluster-nodes.md
147-
- name: How-to
148-
items:
149-
- name: Manage
150-
items:
151-
- name: Backup & restore
152-
href: backup-restore-postgresql-hyperscale.md
153-
- name: Change PostgreSQL port
154-
href: change-postgresql-port.md
155-
- name: Configure & scale
156-
items:
157-
- name: Show configuration
158-
href: show-configuration-postgresql-hyperscale-server-group.md
159-
- name: Scale out|in worker nodes
160-
href: scale-out-in-postgresql-hyperscale-server-group.md
161-
- name: Scale up|down memory & vCores
162-
href: scale-up-down-postgresql-hyperscale-server-group-using-cli.md
163-
- name: Configure server parameters
164-
href: configure-server-parameters-postgresql-hyperscale.md
165-
- name: Delete
166-
href: delete-postgresql-hyperscale-server-group.md
167-
- name: List server groups
168-
href: list-server-groups-postgres-hyperscale.md
169-
- name: Monitoring, log analytics, billing information (portal)
170-
href: monitoring-log-analytics-azure-portal-postgresql.md
171-
- name: Secure
172-
href: configure-security-postgres-hyperscale.md
173-
- name: Manage server group (Azure Data Studio)
174-
href: manage-postgresql-hyperscale-server-group-with-azure-data-studio.md
175-
- name: Use PostgreSQL extensions
176-
href: using-extensions-in-postgresql-hyperscale-server-group.md
177-
- name: Migrate
178-
items:
179-
- name: Migrate PostgreSQL data into a PostgreSQL Hyperscale server group
180-
href: migrate-postgresql-data-into-postgresql-hyperscale-server-group.md
181-
- name: Import the sample database AdventureWorks
182-
href: restore-adventureworks-sample-db-into-postgresql-hyperscale-server-group.md
183-
- name: Troubleshoot
184-
href: troubleshoot-postgresql-hyperscale-server-group.md
185119
- name: Azure Arc-enabled SQL Managed Instance
186120
items:
187121
- name: Overview

articles/bastion/configuration-settings.md

Lines changed: 24 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
---
22
title: 'About Azure Bastion configuration settings'
33
description: Learn about the available configuration settings for Azure Bastion.
4-
services: bastion
54
author: cherylmc
65
ms.service: bastion
76
ms.topic: conceptual
8-
ms.date: 01/14/2022
7+
ms.date: 08/03/2022
98
ms.author: cherylmc
10-
ms.custom: ignite-fall-2021
9+
1110
---
1211

1312
# About Bastion configuration settings
@@ -19,19 +18,22 @@ The sections in this article discuss the resources and settings for Azure Bastio
1918
A SKU is also known as a Tier. Azure Bastion supports two SKU types: Basic and Standard. The SKU is configured in the Azure portal during the workflow when you configure Bastion. You can [upgrade a Basic SKU to a Standard SKU](#upgradesku).
2019

2120
* The **Basic SKU** provides base functionality, enabling Azure Bastion to manage RDP/SSH connectivity to virtual machines (VMs) without exposing public IP addresses on the target application VMs.
22-
* The **Standard SKU** enables premium features that allow Azure Bastion to manage remote connectivity at a larger scale.
21+
* The **Standard SKU** enables premium features.
2322

24-
The following table shows features and corresponding SKUs.
23+
The following table shows the availability of features per corresponding SKU.
2524

2625
[!INCLUDE [Azure Bastion SKUs](../../includes/bastion-sku.md)]
2726

27+
### Specify SKU
28+
2829
Currently, you must use the Azure portal if you want to specify the Standard SKU. If you use the Azure CLI or Azure PowerShell to configure Bastion, the SKU can't be specified and defaults to the Basic SKU.
2930

30-
| Method | Value | Links |
31+
| Method | SKU Value | Links |
3132
| --- | --- | --- |
32-
| Azure portal | Tier - Basic or <br>Standard | [Quickstart - Configure Bastion from VM settings](quickstart-host-portal.md)<br>[Tutorial - Configure Bastion](tutorial-create-host-portal.md) |
33-
| Azure PowerShell | Basic only - no settings |[Configure Bastion - PowerShell](bastion-create-host-powershell.md) |
34-
| Azure CLI | Basic only - no settings | [Configure Bastion - CLI](create-host-cli.md) |
33+
| Azure portal | Tier - Basic or Standard | [Tutorial](tutorial-create-host-portal.md) |
34+
| Azure portal | Tier - Basic| [Quickstart](quickstart-host-portal.md) |
35+
| Azure PowerShell | Basic |[How-to](bastion-create-host-powershell.md) |
36+
| Azure CLI | Basic| [How-to](create-host-cli.md) |
3537

3638
### <a name="upgradesku"></a>Upgrade a SKU
3739

@@ -45,7 +47,7 @@ You can configure this setting using the following method:
4547

4648
| Method | Value | Links |
4749
| --- | --- | --- |
48-
| Azure portal |Tier | [Upgrade a SKU](upgrade-sku.md)|
50+
| Azure portal |Tier | [How-to](upgrade-sku.md)|
4951

5052
## <a name="subnet"></a>Azure Bastion subnet
5153

@@ -65,7 +67,7 @@ You can configure this setting using the following methods:
6567

6668
| Method | Value | Links |
6769
| --- | --- |--- |
68-
| Azure portal | Subnet |[Quickstart - Configure Bastion from VM settings](quickstart-host-portal.md)<br>[Tutorial - Configure Bastion](tutorial-create-host-portal.md)|
70+
| Azure portal | Subnet |[Quickstart](quickstart-host-portal.md)<br>[Tutorial](tutorial-create-host-portal.md)|
6971
| Azure PowerShell | -subnetName|[cmdlet](/powershell/module/az.network/new-azbastion#parameters) |
7072
| Azure CLI | --subnet-name | [command](/cli/azure/network/vnet#az-network-vnet-create) |
7173

@@ -80,11 +82,11 @@ Azure Bastion requires a Public IP address. The Public IP must have the followin
8082

8183
You can configure this setting using the following methods:
8284

83-
| Method | Value | Links |
84-
| --- | --- |--- |
85-
| Azure portal | Public IP address |[Azure portal](https://portal.azure.com)|
86-
| Azure PowerShell | -PublicIpAddress| [cmdlet](/powershell/module/az.network/new-azbastion#parameters) |
87-
| Azure CLI | --public-ip create |[command](/cli/azure/network/public-ip) |
85+
| Method | Value | Links | Requires Standard SKU|
86+
| --- | --- |--- | -- |
87+
| Azure portal | Public IP address |[Azure portal](https://portal.azure.com)| Yes |
88+
| Azure PowerShell | -PublicIpAddress| [cmdlet](/powershell/module/az.network/new-azbastion#parameters) | Yes |
89+
| Azure CLI | --public-ip create |[command](/cli/azure/network/public-ip) | Yes |
8890

8991
## <a name="instance"></a>Instances and host scaling
9092

@@ -96,16 +98,16 @@ Instances are created in the AzureBastionSubnet. To allow for host scaling, the
9698

9799
You can configure this setting using the following methods:
98100

99-
| Method | Value | Links |
100-
| --- | --- | --- |
101-
| Azure portal |Instance count | [Azure portal steps](configure-host-scaling.md)|
102-
| Azure PowerShell | ScaleUnit | [PowerShell steps](configure-host-scaling-powershell.md) |
101+
| Method | Value | Links | Requires Standard SKU |
102+
| --- | --- | --- | ---|
103+
| Azure portal |Instance count | [How-to](configure-host-scaling.md)| Yes
104+
| Azure PowerShell | ScaleUnit | [How-to](configure-host-scaling-powershell.md) | Yes |
103105

104106
## <a name="ports"></a>Custom ports
105107

106-
You can specify the port that you want to use to connect to your VMs. By default, the inbound ports used to connect are 3389 for RDP and 22 for SSH. If you configure a custom port value, you need to specify that value when you connect to the VM.
108+
You can specify the port that you want to use to connect to your VMs. By default, the inbound ports used to connect are 3389 for RDP and 22 for SSH. If you configure a custom port value, specify that value when you connect to the VM.
107109

108-
Custom port values are supported for the Standard SKU only. If your Bastion deployment uses the Basic SKU, you can easily [upgrade a Basic SKU to a Standard SKU](#upgradesku).
110+
Custom port values are supported for the Standard SKU only.
109111

110112
## Next steps
111113

Binary file not shown.
50 KB
Loading

articles/bastion/upgrade-sku.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,31 +2,31 @@
22
title: 'Upgrade a SKU'
33
titleSuffix: Azure Bastion
44
description: Learn how to change Tiers from the Basic to the Standard SKU.
5-
services: bastion
65
author: cherylmc
76
ms.service: bastion
87
ms.topic: how-to
9-
ms.date: 08/30/2021
8+
ms.date: 08/02/2022
109
ms.author: cherylmc
11-
# Customer intent: As someone with a networking background, I want to upgrade to the Standard SKU.
12-
ms.custom: ignite-fall-2021
10+
1311
---
1412

1513
# Upgrade a SKU
1614

17-
This article helps you upgrade from the Basic Tier (SKU) to Standard. Once you upgrade, you can't revert back to the Basic SKU without deleting and reconfiguring Bastion. Currently, this setting can be configured in the Azure portal only. For more information about host scaling, see [Configuration settings- SKUs](configuration-settings.md#skus).
15+
This article helps you upgrade from the Basic Tier (SKU) to Standard. Once you upgrade, you can't revert back to the Basic SKU without deleting and reconfiguring Bastion. Currently, this setting can be configured in the Azure portal only. For more information about features and SKUs, see [Configuration settings](configuration-settings.md).
1816

1917
## Configuration steps
2018

2119
1. Sign in to the [Azure portal](https://portal.azure.com).
2220
1. In the Azure portal, go to your Bastion host.
23-
1. On the **Configuration** page, for **Tier**, select **Standard** from the dropdown.
21+
1. On the **Configuration** page, for **Tier**, select **Standard**.
22+
23+
:::image type="content" source="./media/upgrade-sku/select-sku.png" alt-text="Screenshot of tier select dropdown with Standard selected." lightbox="./media/upgrade-sku/select-sku.png":::
2424

25-
:::image type="content" source="./media/upgrade-sku/select-sku.png" alt-text="Screenshot of tier select dropdown with Standard selected." lightbox="./media/upgrade-sku/select-sku-expand.png":::
25+
1. You can add features at the same time you upgrade the SKU. You don't need to upgrade the SKU and then go back to add the features as a separate step.
2626

27-
1. Click **Apply** to apply changes.
27+
1. Click **Apply** to apply changes. The bastion host will update. This takes about 10 minutes to complete.
2828

2929
## Next steps
3030

31-
* See [Configuration settings](configuration-settings.md) for additional configuration information.
31+
* See [Configuration settings](configuration-settings.md) for more configuration information.
3232
* Read the [Bastion FAQ](bastion-faq.md).
2.17 KB
Loading
34.2 KB
Loading
-3.07 KB
Loading
-3.13 KB
Loading

0 commit comments

Comments
 (0)