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/saas-apps/hornbill-tutorial.md
+15-19Lines changed: 15 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.subservice: saas-app-tutorial
10
10
ms.workload: identity
11
11
ms.topic: tutorial
12
-
ms.date: 11/21/2022
12
+
ms.date: 04/19/2023
13
13
ms.author: jeedes
14
14
---
15
15
# Tutorial: Azure AD SSO integration with Hornbill
@@ -116,37 +116,33 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
116
116
117
117
1. In a different web browser window, log in to Hornbill as a Security Administrator.
118
118
119
-
2. On the Home page, click **System**.
119
+
2. On the Home page, click the **Configuration** settings icon at the bottom left of the page.
120
120
121
-

121
+

122
122
123
-
3. Navigate to **Security**.
123
+
3. Navigate to **Platform Configuration**.
124
124
125
-

125
+

126
126
127
-
4. Click **SSO Profiles**.
127
+
4. Click **SSO Profiles** under Security.
128
128
129
-

129
+

130
130
131
-
5. On the right side of the page, click on **Add logo**.
131
+
5. On the right side of the page, click on **+ Create New Profile**.
132
132
133
-

133
+

134
134
135
-
6. On the **Profile Details** bar, click on **Import SAML Meta logo**.
135
+
6. On the **Profile Details** bar, click on the **Import IDP Meta Data** button.
136
136
137
-

137
+

138
138
139
-
7. On the Pop-up page in the **URL** text box, paste the **App Federation Metadata Url**, which you have copied from Azure portal and click **Process**.
139
+
7. On the pop-up, in the **URL** text box, paste the **App Federation Metadata Url**, which you have copied from Azure portal and click **Process**.
@@ -155,7 +151,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
155
151
In this section, a user called Britta Simon is created in Hornbill. Hornbill supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Hornbill, a new one is created after authentication.
156
152
157
153
> [!Note]
158
-
> If you need to create a user manually, contact[Hornbill Client support team](https://www.hornbill.com/support/?request/).
154
+
> If you need to create a user manually, contact[Hornbill Client support team](https://www.hornbill.com/support/?request/).
Copy file name to clipboardExpand all lines: articles/governance/management-groups/overview.md
+5-13Lines changed: 5 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Organize your resources with management groups - Azure Governance
3
3
description: Learn about the management groups, how their permissions work, and how to use them.
4
-
ms.date: 01/24/2023
4
+
ms.date: 04/20/2023
5
5
ms.topic: overview
6
6
author: tfitzmac
7
7
ms.author: tomfitz
@@ -139,11 +139,10 @@ details on moving items within the hierarchy.
139
139
140
140
## Azure custom role definition and assignment
141
141
142
-
Azure custom role support for management groups is currently in preview with some
143
-
[limitations](#limitations). You can define the management group scope in the Role Definition's
144
-
assignable scope. That Azure custom role will then be available for assignment on that management
145
-
group and any management group, subscription, resource group, or resource under it. This custom role
146
-
will inherit down the hierarchy like any built-in role.
142
+
You can define a management group as an assignable scope in an Azure custom role definition.
143
+
The Azure custom role will then be available for assignment on that management
144
+
group and any management group, subscription, resource group, or resource under it. The custom role
145
+
will inherit down the hierarchy like any built-in role. For information about the limitations with custom roles and management groups, see [Limitations](#limitations).
147
146
148
147
### Example definition
149
148
@@ -232,13 +231,6 @@ There are limitations that exist when using custom roles on management groups.
232
231
definition's assignable scope. If there's a typo or an incorrect management group ID listed, the
233
232
role definition is still created.
234
233
235
-
> [!IMPORTANT]
236
-
> Adding a management group to `AssignableScopes` is currently in preview. This preview version is
237
-
> provided without a service-level agreement, and it's not recommended for production workloads.
238
-
> Certain features might not be supported or might have constrained capabilities. For more
239
-
> information, see
240
-
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
241
-
242
234
## Moving management groups and subscriptions
243
235
244
236
To move a management group or subscription to be a child of another management group, three rules
Copy file name to clipboardExpand all lines: articles/role-based-access-control/custom-roles.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ manager: amycolannino
7
7
ms.service: role-based-access-control
8
8
ms.topic: conceptual
9
9
ms.workload: identity
10
-
ms.date: 04/05/2023
10
+
ms.date: 04/20/2023
11
11
ms.author: rolyon
12
12
---
13
13
14
14
# Azure custom roles
15
15
16
-
If the [Azure built-in roles](built-in-roles.md) don't meet the specific needs of your organization, you can create your own custom roles. Just like built-in roles, you can assign custom roles to users, groups, and service principals at management group (in preview only), subscription, and resource group scopes.
16
+
If the [Azure built-in roles](built-in-roles.md) don't meet the specific needs of your organization, you can create your own custom roles. Just like built-in roles, you can assign custom roles to users, groups, and service principals at management group, subscription, and resource group scopes.
17
17
18
18
Custom roles can be shared between subscriptions that trust the same Azure AD tenant. There is a limit of **5,000** custom roles per tenant. (For Azure China 21Vianet, the limit is 2,000 custom roles.) Custom roles can be created using the Azure portal, Azure PowerShell, Azure CLI, or the REST API.
0 commit comments