Skip to content

Commit 36eb583

Browse files
authored
Merge pull request #97225 from MicrosoftDocs/master
11/26 AM Publish
2 parents 85e7fcc + ec21799 commit 36eb583

File tree

67 files changed

+790
-448
lines changed

Some content is hidden

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

67 files changed

+790
-448
lines changed

articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Record the **Application (client) ID** for use in a later step.
3939

4040
## Configure the sample
4141

42-
In this tutorial, you configure a sample that you can download from GitHub. The sample WPF desktop application demonstrates sign-up, sign-in, and can call a protected web API in Azure AD B2C. [Download a zip file](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop/archive/master.zip), [browse the repo](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop), or clone the sample from GitHub.
42+
In this tutorial, you configure a sample that you can download from GitHub. The sample WPF desktop application demonstrates sign-up, sign-in, and can call a protected web API in Azure AD B2C. [Download a zip file](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop/archive/msalv3.zip), [browse the repo](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop), or clone the sample from GitHub.
4343

4444
```
4545
git clone https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop.git

articles/active-directory/devices/manage-stale-devices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ If your device is under control of Intune or any other MDM solution, retire the
8888

8989
### System-managed devices
9090

91-
Don't delete system-managed devices. These are generally devices such as auto-pilot. Once deleted, these devices can't be reprovisioned. The new `get-msoldevice` cmdlet excludes system-managed devices by default.
91+
Don't delete system-managed devices. These are generally devices such as Autopilot. Once deleted, these devices can't be reprovisioned. The new `get-msoldevice` cmdlet excludes system-managed devices by default.
9292

9393
### Hybrid Azure AD joined devices
9494

@@ -124,7 +124,7 @@ Disable or delete Azure AD registered devices in the Azure AD.
124124
125125
## Clean up stale devices in the Azure portal
126126

127-
While you can cleanup stale devices in the Azure portal, it is more efficient, to handle this process using a PowerShell script. Use the latest PowerShell V1 module to use the timestamp filter and to filter out system-managed devices such as auto-pilot. At this point, using PowerShell V2 is not recommended.
127+
While you can cleanup stale devices in the Azure portal, it is more efficient, to handle this process using a PowerShell script. Use the latest PowerShell V1 module to use the timestamp filter and to filter out system-managed devices such as Autopilot. At this point, using PowerShell V2 is not recommended.
128128

129129
A typical routine consists of the following steps:
130130

articles/active-directory/hybrid/how-to-connect-password-hash-synchronization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ The synchronization of a password has no impact on the Azure user who is signed
155155

156156
## Password hash sync process for Azure AD Domain Services
157157

158-
If you use Azure AD Domain Services to provide legacy authentication for applications and services that need to use Keberos, LDAP, or NTLM, some additional processes are part of the password hash synchronization flow. Azure AD Connect uses the additional following process to synchronize password hashes to Azure AD for use in Azure AD Domain Services:
158+
If you use Azure AD Domain Services to provide legacy authentication for applications and services that need to use Kerberos, LDAP, or NTLM, some additional processes are part of the password hash synchronization flow. Azure AD Connect uses the additional following process to synchronize password hashes to Azure AD for use in Azure AD Domain Services:
159159

160160
> [!IMPORTANT]
161161
> Azure AD Connect should only be installed and configured for synchronization with on-premises AD DS environments. It's not supported to install Azure AD Connect in an Azure AD DS managed domain to synchronize objects back to Azure AD.

articles/active-directory/users-groups-roles/groups-dynamic-membership.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.workload: identity
1010
ms.subservice: users-groups-roles
1111
ms.topic: article
12-
ms.date: 11/08/2019
12+
ms.date: 11/27/2019
1313
ms.author: curtand
1414
ms.reviewer: krbain
1515
ms.custom: it-pro
@@ -27,7 +27,7 @@ When any attributes of a user or device change, the system evaluates all dynamic
2727

2828
> [!NOTE]
2929
> This feature requires an Azure AD Premium P1 license for each unique user that is a member of one or more dynamic groups. You don't have to assign licenses to users for them to be members of dynamic groups, but you must have the minimum number of licenses in the tenant to cover all such users. For example, if you had a total of 1,000 unique users in all dynamic groups in your tenant, you would need at least 1,000 licenses for Azure AD Premium P1 to meet the license requirement.
30-
>
30+
> No license is required for devices that are members of a dynamic device group.
3131
3232
## Rule builder in the Azure portal
3333

articles/aks/tutorial-kubernetes-scale.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ azure-vote-front-3309479140-qphz8 1/1 Running 0 3m
7171
Kubernetes supports [horizontal pod autoscaling][kubernetes-hpa] to adjust the number of pods in a deployment depending on CPU utilization or other select metrics. The [Metrics Server][metrics-server] is used to provide resource utilization to Kubernetes, and is automatically deployed in AKS clusters versions 1.10 and higher. To see the version of your AKS cluster, use the [az aks show][az-aks-show] command, as shown in the following example:
7272

7373
```azurecli
74-
az aks show --resource-group myResourceGroup --name myAKSCluster --query kubernetesVersion
74+
az aks show --resource-group myResourceGroup --name myAKSCluster --query kubernetesVersion --output table
7575
```
7676

7777
> [!NOTE]

articles/api-management/api-management-howto-add-products.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ In this tutorial, you learn how to:
5353
| Requires approval | Check **Require approval** if you want an administrator to review and accept or reject subscription attempts to this product. If the box is unchecked, subscription attempts are auto-approved. |
5454
| Subscription count limit | To limit the count of multiple simultaneous subscriptions, enter the subscription limit. |
5555
| Legal terms | You can include the terms of use for the product which subscribers must accept in order to use the product. |
56-
| APIs | Products are associations of one or more APIs. You can include a number of APIs and offer them to developers through the developer portal. <br/> You can add an existing API during the product creation. You can add an API to the product later, either from the Products **Settings** page or while creating an API. |
56+
| APIs | Products are associations of one or more APIs. You can include a number of APIs and offer them to developers through the developer portal. <br/> You can add an existing API during the product creation. You can add an API to the product later, either from the Product's **Settings** page or while creating an API. |
5757

5858
3. Click **Create** to create the new product.
5959

@@ -63,7 +63,7 @@ You can continue configuring the product after saving it by choosing the **Setti
6363

6464
View/add subscribers to the product from the **Subscriptions** tab.
6565

66-
Set visibility of a product for developers or guest from the **Access control** tab.
66+
Set visibility of a product for developers or guests from the **Access control** tab.
6767

6868
## <a name="add-apis"> </a>Add APIs to a product
6969

articles/azure-databricks/store-secrets-azure-key-vault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ Sign in to the [Azure portal](https://portal.azure.com/).
124124

125125
4. Once your Azure Databricks workspace is open in a separate window, append **#secrets/createScope** to the URL. The URL should have the following format:
126126

127-
**https://<\location>.azuredatabricks.net/?o=<\id>#secrets/createScope**.
127+
**https://<\location>.azuredatabricks.net/#secrets/createScope**.
128128

129129
5. Enter a scope name, and enter the Azure Key Vault DNS name and Resource ID you saved earlier. Save the scope name in a text editor for use later in this tutorial. Then, select **Create**.
130130

articles/azure-government/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@
1515
href: documentation-government-get-started-connect-with-cli.md
1616
- name: PowerShell
1717
href: documentation-government-get-started-connect-with-ps.md
18+
- name: Visual Studio
19+
href: documentation-government-connect-vs.md
1820
- name: Tutorials
1921
items:
2022
- name: Deploy App Services
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: Connect to Azure Government with Visual Studio | Microsoft Docs
3+
description: This quickstart shows how to connect to Azure Government with Visual Studio
4+
services: azure-government
5+
cloud: gov
6+
documentationcenter: ''
7+
author: yujhongmicrosoft
8+
manager: zakramer
9+
10+
ms.service: azure-government
11+
ms.devlang: na
12+
ms.topic: quickstart
13+
ms.tgt_pltfrm: na
14+
ms.workload: azure-government
15+
ms.date: 10/31/2019
16+
ms.author: yujhong
17+
18+
---
19+
20+
# Quickstart: Connect to Azure Government with Visual Studio
21+
22+
Microsoft Azure Government delivers a dedicated cloud with world-class security and compliance, enabling US government agencies and their partners to transform their workloads to the cloud. To manage your Azure Government cloud workloads and applications you can connect to the Azure Government using different tools, as described in the following video.
23+
24+
This quickstart shows how to connect to your Azure Government accounts and subscriptions with Visual Studio.
25+
26+
If you don't have an Azure Government subscription, create a [free account](https://azure.microsoft.com/global-infrastructure/government/request/) before you begin.
27+
28+
## Prerequisites
29+
30+
* Review [Guidance for developers](documentation-government-developer-guide.md).<br/> This article discusses Azure Government's unique URLs and endpoints for managing your environment. You must know about these endpoints in order to connect to Azure Government.
31+
* Review [Compare Azure Government and global Azure](compare-azure-government-global-azure.md) and click on a service of interest to see variations between Azure Government and global Azure.
32+
* Install <a href="https://www.visualstudio.com/downloads/" target="_blank">Visual Studio 2019</a>.
33+
34+
## Sign in to Azure Government
35+
Open up Visual Studio and click **Tools** > **Options**.
36+
37+
![VS-1](./media/connect-to-vs-1.png)
38+
39+
Then navigate to **Environment** > **Accounts** and under "Registered Azure Clouds" you can see which cloud endpoints you already have registered. In order to add Azure Government, you must click the "Add" button and will see the dropdown below:
40+
41+
![VS-2](./media/connect-to-vs-2.png)
42+
![VS-3](./media/connect-to-vs-3.png)
43+
44+
From this dropdown, you can choose "Azure U.S. Government" and click add. Once you have done this you should be able to see "Azure U.S. Government" under "Registered Azure Clouds".
45+
46+
![VS-4](./media/connect-to-vs-4.png)
47+
![VS-5](./media/connect-to-vs-5.png)
48+
49+
Then you can click on the blue "Manage Accounts" link in the top-left corner and choose "Azure US Government" to access an Azure Government account.
50+
51+
![VS-6](./media/connect-to-vs-6.png)
52+
![VS-7](./media/connect-to-vs-7.png)
53+
54+
You are prompted to sign in, and once you have entered your credentials you will be able to see your account and subscriptions populate on the left-hand side. Now you are free to manage and interact with your Azure Government resources in Visual Studio!
55+
56+
## Next steps
57+
58+
This quickstart showed you how to use Visual Studio to connect to Azure Government. Once you are connected to Azure Government, you may want to explore Azure services. Make sure you check out the variations, described in [Compare Azure Government and global Azure](compare-azure-government-global-azure.md). To learn more about Azure services continue to the Azure documentation.
59+
60+
> [!div class="nextstepaction"]
61+
> [Azure documentation](https://docs.microsoft.com/azure/).

articles/azure-government/documentation-government-developer-guide.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,7 @@ Navigate through the links below to get started using Azure Government.
5757
* [Login to Azure Government Portal](documentation-government-get-started-connect-with-portal.md)
5858
* [Connect with PowerShell](documentation-government-get-started-connect-with-ps.md)
5959
* [Connect with CLI](documentation-government-get-started-connect-with-cli.md)
60+
* [Connect with Visual Studio](documentation-government-connect-vs.md)
6061
* [Connect to Azure Storage](documentation-government-get-started-connect-to-storage.md)
6162
* [Connect with Azure SDK for Python](/azure/python/python-sdk-azure-multi-cloud)
6263

0 commit comments

Comments
 (0)