You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/devices/device-management-azure-portal.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,25 @@ To view or copy BitLocker keys, you need to be the owner of the device or have o
107
107
- Security Administrator
108
108
- Security Reader
109
109
110
+
## Block users from viewing their BitLocker keys (preview)
111
+
In this preivew, admins can block self-service BitLocker key access to the registered owner of the device. Default users without the BitLocker read permission will be unable to view or copy their BitLocker key(s) for their owned devices.
112
+
113
+
To disable/enable self-service BitLocker recovery:
In this preview, you have the ability to infinitely scroll, reorder columns, and select all devices. You can filter the device list by these device attributes:
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-nonaad.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,6 +103,7 @@ To complete these steps, you need an SSH client. If you are using Windows, you
103
103
2.**Connect** to the VM with the SSH client of your choice.
104
104
3. In the terminal window, use CURL to make a request to the local managed identities for Azure resources endpoint to get an access token for Azure Key Vault.
105
105
106
+
106
107
The CURL request for the access token is below.
107
108
108
109
```bash
@@ -147,4 +148,4 @@ Alternatively you may also do this via [PowerShell or the CLI](../../azure-resou
147
148
In this tutorial, you learned how to use a Linux VM system-assigned managed identity to access Azure Key Vault. To learn more about Azure Key Vault see:
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/sonarqube-tutorial.md
+32-29Lines changed: 32 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: 'Tutorial: Azure AD SSO integration with Sonarqube'
3
-
description: Learn how to configure single sign-on between Azure Active Directory and Sonarqube.
2
+
title: 'Tutorial: Azure AD SSO integration with SonarQube'
3
+
description: Learn how to configure single sign-on between Azure Active Directory and SonarQube.
4
4
services: active-directory
5
5
author: jeevansd
6
6
manager: CelesteDG
@@ -13,59 +13,62 @@ ms.date: 06/25/2021
13
13
ms.author: jeedes
14
14
---
15
15
16
-
# Tutorial: Azure AD SSO integration with Sonarqube
16
+
# Tutorial: Azure AD SSO integration with SonarQube
17
17
18
-
In this tutorial, you'll learn how to integrate Sonarqube with Azure Active Directory (Azure AD). When you integrate Sonarqube with Azure AD, you can:
18
+
In this tutorial, you'll learn how to integrate SonarQube with Azure Active Directory (Azure AD). When you integrate SonarQube with Azure AD, you can:
19
19
20
-
* Control in Azure AD who has access to Sonarqube.
21
-
* Enable your users to be automatically signed-in to Sonarqube with their Azure AD accounts.
20
+
* Control in Azure AD who has access to SonarQube.
21
+
* Enable your users to be automatically signed-in to SonarQube with their Azure AD accounts.
22
22
* Manage your accounts in one central location - the Azure portal.
23
23
24
24
## Prerequisites
25
25
26
26
To get started, you need the following items:
27
27
28
28
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
29
-
* Sonarqube single sign-on (SSO) enabled subscription.
29
+
* SonarQube single sign-on (SSO) enabled subscription.
30
+
31
+
> [!NOTE]
32
+
> Help on installing SonarQube can be found in the [online documentation](https://docs.sonarqube.org/latest/setup/install-server/).
30
33
31
34
## Scenario description
32
35
33
36
In this tutorial, you configure and test Azure AD SSO in a test environment.
34
37
35
-
*Sonarqube supports **SP** initiated SSO.
38
+
*SonarQube supports **SP** initiated SSO.
36
39
37
40
> [!NOTE]
38
41
> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
39
42
40
-
## Add Sonarqube from the gallery
43
+
## Add SonarQube from the gallery
41
44
42
-
To configure the integration of Sonarqube into Azure AD, you need to add Sonarqube from the gallery to your list of managed SaaS apps.
45
+
To configure the integration of SonarQube into Azure AD, you need to add SonarQube from the gallery to your list of managed SaaS apps.
43
46
44
47
1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
45
48
1. On the left navigation pane, select the **Azure Active Directory** service.
46
49
1. Navigate to **Enterprise Applications** and then select **All Applications**.
47
50
1. To add new application, select **New application**.
48
-
1. In the **Add from the gallery** section, type **Sonarqube** in the search box.
49
-
1. Select **Sonarqube** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
51
+
1. In the **Add from the gallery** section, type **SonarQube** in the search box.
52
+
1. Select **SonarQube** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
50
53
51
-
## Configure and test Azure AD SSO for Sonarqube
54
+
## Configure and test Azure AD SSO for SonarQube
52
55
53
-
Configure and test Azure AD SSO with Sonarqube using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Sonarqube.
56
+
Configure and test Azure AD SSO with SonarQube using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in SonarQube.
54
57
55
-
To configure and test Azure AD SSO with Sonarqube, perform the following steps:
58
+
To configure and test Azure AD SSO with SonarQube, perform the following steps:
56
59
57
60
1.**[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
58
61
1.**[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
59
62
1.**[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
60
-
1.**[Configure Sonarqube SSO](#configure-sonarqube-sso)** - to configure the single sign-on settings on application side.
61
-
1.**[Create Sonarqube test user](#create-sonarqube-test-user)** - to have a counterpart of B.Simon in Sonarqube that is linked to the Azure AD representation of user.
63
+
1.**[Configure SonarQube SSO](#configure-sonarqube-sso)** - to configure the single sign-on settings on application side.
64
+
1.**[Create SonarQube test user](#create-sonarqube-test-user)** - to have a counterpart of B.Simon in SonarQube that is linked to the Azure AD representation of user.
62
65
1.**[Test SSO](#test-sso)** - to verify whether the configuration works.
63
66
64
67
## Configure Azure AD SSO
65
68
66
69
Follow these steps to enable Azure AD SSO in the Azure portal.
67
70
68
-
1. In the Azure portal, on the **Sonarqube** application integration page, find the **Manage** section and select **single sign-on**.
71
+
1. In the Azure portal, on the **SonarQube** application integration page, find the **Manage** section and select **single sign-on**.
69
72
1. On the **Select a single sign-on method** page, select **SAML**.
70
73
1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
71
74
@@ -93,7 +96,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
@@ -111,19 +114,19 @@ In this section, you'll create a test user in the Azure portal called B.Simon.
111
114
112
115
### Assign the Azure AD test user
113
116
114
-
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Sonarqube.
117
+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to SonarQube.
115
118
116
119
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
117
-
1. In the applications list, select **Sonarqube**.
120
+
1. In the applications list, select **SonarQube**.
118
121
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
119
122
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
120
123
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
121
124
1. If you are expecting a role to be assigned to the users, you can select it from the **Select a role** dropdown. If no role has been set up for this app, you see "Default Access" role selected.
122
125
1. In the **Add Assignment** dialog, click the **Assign** button.
123
126
124
-
## Configure Sonarqube SSO
127
+
## Configure SonarQube SSO
125
128
126
-
1. Open a new web browser window and sign into your Sonarqube company site as an administrator.
129
+
1. Open a new web browser window and sign into your SonarQube company site as an administrator.
127
130
128
131
1. Click on **Administration > Configuration > Security** and go to the **SAML Plugin** perform the following steps.
129
132
@@ -160,20 +163,20 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
160
163
161
164
j. Click **Save**.
162
165
163
-
### Create Sonarqube test user
166
+
### Create SonarQube test user
164
167
165
-
In this section, you create a user called B.Simon in Sonarqube. Work with [Sonarqube Client support team](https://sonarsource.com/company/contact/) to add the users in the Sonarqube platform. Users must be created and activated before you use single sign-on.
168
+
In this section, you create a user called B.Simon in SonarQube. Work with [SonarQube Client support team](https://sonarsource.com/company/contact/) to add the users in the SonarQube platform. Users must be created and activated before you use single sign-on.
166
169
167
170
## Test SSO
168
171
169
172
In this section, you test your Azure AD single sign-on configuration with following options.
170
173
171
-
* Click on **Test this application** in Azure portal. This will redirect to Sonarqube Sign-on URL where you can initiate the login flow.
174
+
* Click on **Test this application** in Azure portal. This will redirect to SonarQube Sign-on URL where you can initiate the login flow.
172
175
173
-
* Go to Sonarqube Sign-on URL directly and initiate the login flow from there.
176
+
* Go to SonarQube Sign-on URL directly and initiate the login flow from there.
174
177
175
-
* You can use Microsoft My Apps. When you click the Sonarqube tile in the My Apps, this will redirect to Sonarqube Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](https://support.microsoft.com/account-billing/sign-in-and-start-apps-from-the-my-apps-portal-2f3b1bae-0e5a-4a86-a33e-876fbd2a4510).
178
+
* You can use Microsoft My Apps. When you click the SonarQube tile in the My Apps, this will redirect to SonarQube Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](https://support.microsoft.com/account-billing/sign-in-and-start-apps-from-the-my-apps-portal-2f3b1bae-0e5a-4a86-a33e-876fbd2a4510).
176
179
177
180
## Next steps
178
181
179
-
* Once you configure the Sonarqube you can enforce session controls, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session controls extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
182
+
* Once you configure SonarQube, you can enforce session controls, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session controls extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
Copy file name to clipboardExpand all lines: articles/aks/cluster-configuration.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,9 @@ By using `containerd` for AKS nodes, pod startup latency improves and node resou
31
31
`Containerd` works on every GA version of Kubernetes in AKS, and in every upstream kubernetes version above v1.19, and supports all Kubernetes and AKS features.
32
32
33
33
> [!IMPORTANT]
34
-
> Clusters with Linux node pools created on Kubernetes v1.19 or greater default to `containerd` for its container runtime. Clusters with node pools on a earlier supported Kubernetes versions receive Docker for their container runtime. Linux node pools will be updated to `containerd` once the node pool Kubernetes version is updated to a version that supports `containerd`. You can still use Docker node pools and clusters on versions below 1.23, but Docker is no longer supported as of September 2022.
34
+
> Clusters with Linux node pools created on Kubernetes v1.19 or greater default to `containerd` for its container runtime. Clusters with node pools on a earlier supported Kubernetes versions receive Docker for their container runtime. Linux node pools will be updated to `containerd` once the node pool Kubernetes version is updated to a version that supports `containerd`.
35
35
>
36
-
> Using `containerd` with Windows Server 2019 node pools is generally available, and will be the only container runtime option in Kubernetes 1.21 and greater. For more details, see [Add a Windows Server node pool with `containerd`][/learn/aks-add-np-containerd].
36
+
> Using `containerd` with Windows Server 2019 node pools is generally available, and will be the only container runtime option in Kubernetes 1.21 and greater. You can still use Docker node pools and clusters on versions below 1.23, but Docker is no longer supported as of September 2022. For more details, see [Add a Windows Server node pool with `containerd`][aks-add-np-containerd].
37
37
>
38
38
> It is highly recommended to test your workloads on AKS node pools with `containerd` prior to using clusters with a Kubernetes version that supports `containerd` for your node pools.
39
39
@@ -232,4 +232,4 @@ az aks show -n aks -g myResourceGroup --query "oidcIssuerProfile.issuerUrl" -ots
Copy file name to clipboardExpand all lines: articles/aks/integrations.md
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Azure Kubernetes Service (AKS) provides additional, supported functionality for
13
13
14
14
## Add-ons
15
15
16
-
Add-ons are a fully-supported way to provide extra capabilities for your AKS cluster. Add-ons' installation, configuration, and lifecycle is managed by AKS. Use `az aks addon` to install an add-on or manage the add-ons for your cluster.
16
+
Add-ons are a fullysupported way to provide extra capabilities for your AKS cluster. Add-ons' installation, configuration, and lifecycle is managed by AKS. Use `az aks addon` to install an add-on or manage the add-ons for your cluster.
17
17
18
18
The following rules are used by AKS for applying updates to installed add-ons:
19
19
@@ -44,6 +44,10 @@ Cluster extensions build on top of certain Helm charts and provide an Azure Reso
44
44
45
45
Both extensions and add-ons are supported ways to add functionality to your AKS cluster. When you install an add-on, the functionality is added as part of the AKS resource provider in the Azure API. When you install an extension, the functionality is added as part of a separate resource provider in the Azure API.
46
46
47
+
## GitHub Actions
48
+
49
+
GitHub Actions helps you automate your software development workflows from within GitHub. For more details on using GitHub Actions with Azure, see [What is GitHub Actions for Azures][github-actions]. For an example of using GitHub Actions with an AKS cluster, see [Build, test, and deploy containers to Azure Kubernetes Service using GitHub Actions][github-actions-aks].
50
+
47
51
## Open source and third-party integrations
48
52
49
53
You can install many open source and third-party integrations on your AKS cluster, but these open-source and third-party integrations are not covered by the [AKS support policy][aks-support-policy].
@@ -99,4 +103,17 @@ The below table shows a few examples of open-source and third-party integrations
0 commit comments