Skip to content

Commit 71cae22

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us417294-vnet-top-freshness
2 parents 9d5c7c2 + a4db996 commit 71cae22

File tree

124 files changed

+1021
-785
lines changed

Some content is hidden

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

124 files changed

+1021
-785
lines changed
Lines changed: 23 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Enable API Center portal - Azure API Center - VS Code extension
3-
description: Enable enterprise developers to view the enterprise's API Center portal including API definitions using the Visual Studio Code Extension for Azure API Center.
2+
title: Enable API Center portal view - Azure API Center - VS Code extension
3+
description: Enable enterprise developers to view the enterprise's API Center portal view including API definitions using the Visual Studio Code Extension for Azure API Center.
44
author: dlepow
55
ms.service: azure-api-center
66
ms.topic: how-to
@@ -10,9 +10,9 @@ ms.custom:
1010
# Customer intent: As an API program manager, I want to enable an API catalog so that app developers in my organization can discover and consume the APIs in my organization's API center without needing to manage the API inventory itself.
1111
---
1212

13-
# Enable and view Azure API Center portal - VS Code extension
13+
# Enable and view Azure API Center portal view - VS Code extension
1414

15-
This article shows how to provide enterprise developers access to the Azure API Center portal in the Visual Studio Code extension for [Azure API Center](overview.md). Using the portal, developers can discover APIs in your Azure API center, view API definitions, and optionally generate API clients when they don't have access to manage the API center itself or add APIs to the inventory. Access to the API Center portal is managed using Microsoft Entra ID and Azure role-based access control.
15+
This article shows how to provide enterprise developers access to the Azure API Center portal view in the Visual Studio Code extension for [Azure API Center](overview.md). Using the portal view, developers can discover APIs in your Azure API center, view API definitions, and optionally generate API clients when they don't have access to manage the API center itself or add APIs to the inventory. Access to the API Center portal view is managed using Microsoft Entra ID and Azure role-based access control.
1616

1717
> [!TIP]
1818
> The Visual Studio Code extension provides more features for API developers who have permissions to manage an Azure API center. For example, API developers can register APIs in the API center directly or using CI/CD pipelines. [Learn more](build-register-apis-vscode-extension.md)
@@ -32,23 +32,23 @@ The following Visual Studio Code extension is optional:
3232

3333
* [Microsoft Kiota extension](https://marketplace.visualstudio.com/items?itemName=ms-graph.kiota) - to generate API clients
3434

35-
## Steps for API center administrators to enable access to API Center portal
35+
## Steps for API center administrators to enable access to API Center portal view
3636

37-
The following sections provide steps for API center administrators to enable enterprise developers to access the API Center portal.
37+
The following sections provide steps for API center administrators to enable enterprise developers to access the API Center portal view.
3838

3939
### Create Microsoft Entra app registration
4040

4141
[!INCLUDE [api-center-portal-app-registration](includes/api-center-portal-app-registration.md)]
4242

43-
### Enable sign-in to API Center portal by Microsoft Entra users and groups
43+
### Enable sign-in to API Center portal view by Microsoft Entra users and groups
4444

45-
Enterprise developers must sign in with a Microsoft account to see the API Center portal for your API center. If needed, [add or invite developers](/entra/external-id/b2b-quickstart-add-guest-users-portal) to your Microsoft Entra tenant.
45+
Enterprise developers must sign in with a Microsoft account to see the API Center portal view for your API center. If needed, [add or invite developers](/entra/external-id/b2b-quickstart-add-guest-users-portal) to your Microsoft Entra tenant.
4646

4747
[!INCLUDE [api-center-portal-user-sign-in](includes/api-center-portal-user-sign-in.md)]
4848

49-
## Steps for enterprise developers to access the API Center portal
49+
## Steps for enterprise developers to access the API Center portal view
5050

51-
Developers can follow these steps to connect and sign in to view an API Center portal using the Visual Studio Code extension. Settings to connect to the API center need to be provided by the API center administrator.
51+
Developers can follow these steps to connect and sign in to view an API Center portal view using the Visual Studio Code extension. Settings to connect to the API center need to be provided by the API center administrator.
5252

5353
### Connect to an API center
5454

@@ -60,29 +60,30 @@ Developers can follow these steps to connect and sign in to view an API Center p
6060

6161
1. Use the **Ctrl+Shift+P** keyboard shortcut to open the Command Palette. Type **Azure API Center: Connect to an API Center** and hit **Enter**.
6262
1. Answer the prompts to input the following information:
63-
1. The runtime URL of your API center, in the format `<service name>.data.<region>.azure-apicenter.ms` (don't prefix with `https://`). Example: `contoso-apic.data.eastus.azure-apicenter.ms`. This runtime URL appears on the **Overview** page of the API center in the Azure portal.
63+
1. The runtime URL of your API center, in the format `<service name>.data.<region>.azure-apicenter.ms` (don't prefix with `https://`). Example: `contoso-apic.data.eastus.azure-apicenter.ms`. This runtime URL appears on the **Overview** page of the API center in the Azure portal view.
64+
6465
1. The application (client) ID from the app registration configured by the administrator in the previous section.
6566
1. The directory (tenant) ID from the app registration configured by the administrator in the previous section.
6667

6768
> [!TIP]
6869
> An API center administrator needs to provide these connection details to developers, or provide a direct link in the following format:
6970
> `vscode://apidev.azure-api-center?clientId=<Client ID>&tenantId=<tenant ID>&runtimeUrl=<service-name>.data.<region>.azure-apicenter.ms`
7071
71-
After you connect to the API center, the name of the API center appears in the API Center portal.
72-
72+
After you connect to the API center, the name of the API center appears in the API Center portal view.
73+
7374
1. To view the APIs in the API center, under the API center name, select **Sign in to Azure**. Sign-in is allowed with a Microsoft account that is assigned the **Azure API Center Data Reader** role in the API center.
7475

75-
:::image type="content" source="media/enable-api-center-portal-vs-code-extension/api-center-pane-initial.png" alt-text="Screenshot of API Center portal in VS Code extension." :::
76-
76+
:::image type="content" source="media/enable-api-center-portal-vs-code-extension/api-center-pane-initial.png" alt-text="Screenshot of the API Center portal view in API Center extension.":::
77+
7778
1. After signing in, select **APIs** to list the APIs in the API center. Expand an API to explore its versions and definitions.
7879

79-
:::image type="content" source="media/enable-api-center-portal-vs-code-extension/api-center-pane-apis.png" alt-text="Screenshot of API Center portal with APIs in VS Code extension." :::
80-
80+
:::image type="content" source="media/enable-api-center-portal-vs-code-extension/api-center-pane-apis.png" alt-text="Screenshot of the API Center API definitions in API Center extension.":::
81+
8182
1. Repeat the preceding steps to connect to more API centers, if access is configured.
8283

83-
### Discover and consume APIs in the API Center portal
84+
### Discover and consume APIs in the API Center portal view
8485

85-
The API Center portal helps enterprise developers discover API details and start API client development. Developers can access the following features by right-clicking on an API definition in the API Center portal:
86+
The API Center portal view helps enterprise developers discover API details and start API client development. Developers can access the following features by right-clicking on an API definition in the API Center portal view:
8687

8788
* **Export API specification document** - Export an API specification from a definition and then download it as a file
8889
* **Generate API client** - Use the Microsoft Kiota extension to generate an API client for their favorite language
@@ -92,35 +93,16 @@ The API Center portal helps enterprise developers discover API details and start
9293

9394
## Troubleshooting
9495

95-
### Error: Cannot read properties of undefined (reading 'nextLink')
96-
97-
Under certain conditions, a user might encounter the following error message after signing into the API Center portal and expanding the APIs list for an API center:
98-
99-
`Error: Cannot read properties of undefined (reading 'nextLink')`
100-
101-
Check that the user is assigned the **Azure API Center Data Reader** role in the API center. If necessary, reassign the role to the user. Then, refresh the API Center portal in the Visual Studio Code extension.
102-
10396
### Unable to sign in to Azure
10497

105-
If users who have been assigned the **Azure API Center Data Reader** role can't complete the sign-in flow after selecting **Sign in to Azure** in the API Center portal, there might be a problem with the configuration of the connection.
98+
If users who have been assigned the **Azure API Center Data Reader** role can't complete the sign-in flow after selecting **Sign in to Azure** in the API Center portal view, there might be a problem with the configuration of the connection.
10699

107100
Check the settings in the app registration you configured in Microsoft Entra ID. Confirm the values of the application (client) ID and the directory (tenant) ID in the app registration and the runtime URL of the API center. Then, set up the connection to the API center again.
108101

109-
### Unable to select Azure API Center permissions in Microsoft Entra ID app registration
110-
111-
If you're unable to request API permissions to Azure API Center in your Microsoft Entra app registration for the API Center portal, check that you are searching for **Azure API Center** (or application ID `c3ca1a77-7a87-4dba-b8f8-eea115ae4573`).
112-
113-
If the app isn't present, there might be a problem with the registration of the **Microsoft.ApiCenter** resource provider in your subscription. You might need to re-register the resource provider. To do this, run the following command in the Azure CLI:
114-
115-
```azurecli
116-
az provider register --namespace Microsoft.ApiCenter
117-
```
118-
119-
After re-registering the resource provider, try again to request API permissions.
120-
121-
122102
## Related content
123103

124104
* [Build and register APIs with the Azure API Center extension for Visual Studio Code](build-register-apis-vscode-extension.md)
125105
* [Best practices for Azure RBAC](../role-based-access-control/best-practices.md)
106+
126107
* [Register a resource provider](../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider)
108+
6.07 KB
Loading
23.2 KB
Loading

articles/application-gateway/tutorial-ingress-controller-add-on-existing.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ To configure more parameters for the above command, see [az aks create](/cli/azu
5757
>[!NOTE]
5858
>If you are planning on using AGIC with an AKS cluster using CNI Overlay, specify the parameter `--aks-custom-headers AKSHTTPCustomFeatures=Microsoft.ContainerService/AppGatewayWithOverlayPreview` to configure AGIC to handle connectivity to the CNI Overlay enabled cluster.
5959
60+
>[!WARNING]
61+
>This document assumes Azure CNI is installed in the AKS cluster. If you are planning on using CNI Overlay, you must ensure Application Gateway and the AKS cluster are part of the same virtual network.
62+
6063
## Deploy a new application gateway
6164

6265
You'll now deploy a new application gateway, to simulate having an existing application gateway that you want to use to load balance traffic to your AKS cluster, **myCluster**. The name of the application gateway will be **myApplicationGateway**, but you'll need to first create a public IP resource, named **myPublicIp**, and a new virtual network called **myVnet** with address space 10.0.0.0/16, and a subnet with address space 10.0.0.0/24 called **mySubnet**, and deploy your application gateway in **mySubnet** using **myPublicIp**.

articles/azure-cache-for-redis/TOC.yml

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@
2020
- name: Create and manage with Azure PowerShell
2121
href: /azure/redis/how-to-manage-redis-cache-powershell
2222
- name: Create and manage with Azure CLI
23-
href: /azure/redis/scripts/create-managed-cache
23+
href: /azure/redis/scripts/create-manage-cache?pivots=azure-cache-redis
2424
- name: Create and manage premium cache with Azure CLI
2525
href: scripts/create-manage-premium-cache-cluster.md
2626
- name: Create Redis cache - Bicep
@@ -93,7 +93,7 @@
9393
- name: Overview
9494
href: cli-samples.md
9595
- name: Create and manage a cache
96-
href: /azure/redis/scripts/create-managed-cache
96+
href: /azure/redis/scripts/create-manage-cache?pivots=azure-cache-redis
9797
- name: Create and manage a premium cache
9898
href: scripts/create-manage-premium-cache-cluster.md
9999

@@ -190,8 +190,6 @@
190190
href: cache-administration.md#update-channel-and-schedule-updates
191191
- name: Configure redis-cli access
192192
href: cache-how-to-redis-cli-tool.md
193-
- name: Create and manage a cache using CLI
194-
href: cache-manage-cli.md
195193
- name: Move between regions
196194
href: cache-moving-resources.md
197195
- name: Publishing Azure Cache for Redis events

0 commit comments

Comments
 (0)