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/governance/entitlement-management-logic-apps-integration.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ These triggers to Logic Apps are controlled in a tab within access package polic
81
81
:::image type="content" source="media/entitlement-management-logic-apps/create-logic-app-extension-details.png" alt-text="Screenshot of creating logic app detail selections.":::
82
82
83
83
> [!NOTE]
84
-
> when creating a new Logic App in this modal, the length of "/subscriptions/{SubscriptionId}/resourceGroups/{RG Name}/providers/Microsoft.Logic/workflows/{Logicapp Name}" cannot exceed 150 characters.
84
+
> When creating a new Logic App in this modal, the length of "/subscriptions/{SubscriptionId}/resourceGroups/{RG Name}/providers/Microsoft.Logic/workflows/{Logicapp Name}" cannot exceed 150 characters.
85
85
86
86
1. In **Review and Create**, review the summary of your custom extension and make sure the details for your Logic App callout are correct. Then select **Create**.
87
87
@@ -94,7 +94,7 @@ These triggers to Logic Apps are controlled in a tab within access package polic
94
94
1. Navigate to the Custom Extensions tab within a Catalog as mentioned earlier.
95
95
96
96
1. Here, you can view all the custom extensions you've created, along with the associated Logic App and information about the custom extension type.
97
-
:::image type="content" source="media/entitlement-management-logic-apps/custom-extension-list.png" alt-text="Screenshot of a list of custom extensions.":::
97
+
:::image type="content" source="media/entitlement-management-logic-apps/custom-extension-list.png" alt-text="Screenshot of a list of custom extensions." lightbox="media/entitlement-management-logic-apps/custom-extension-list.png":::
98
98
1. Along with the Logic App name, the column Type dictates whether the custom extension was created in the new V2 auth model (after March 17, 2023), or the original model. If a custom extension was created in the new model, the Type column matches the selected type from the configuration modal that is either “*assignment request*” or “*pre-expiration*”. For older custom extensions, the type shows “*custom access package*”.
99
99
100
100
1. The Token Security column shows the associated auth security framework used when creating the custom extension. New V2 custom extensions show “*proof-of-possession*” (PoP) as the token security type. Older custom extensions show “regular”.
The following flow diagram shows the entitlement management callout to Logic Apps workflow:
178
-
:::image type="content" source="media/entitlement-management-logic-apps/extensibility-diagram-flow.png" alt-text="A screenshot of the extensibility user diagram.":::
178
+
:::image type="content" source="media/entitlement-management-logic-apps/extensibility-diagram-flow.png" alt-text="A screenshot of the extensibility user diagram." lightbox="media/entitlement-management-logic-apps/extensibility-diagram-flow.png":::
An approver sees the string specified in the resume request payload under `customExtensionStageInstanceDetail` as shown in the payload located in [Configuring custom extensions that pause entitlement management processes](entitlement-management-logic-apps-integration.md#configuring-custom-extensions-that-pause-entitlement-management-processes).
233
-
:::image type="content" source="media/entitlement-management-logic-apps/extensibility-approver-experience.png" alt-text="Screenshot of the approver screen.":::
233
+
:::image type="content" source="media/entitlement-management-logic-apps/extensibility-approver-experience.png" alt-text="Screenshot of the approver screen." lightbox="media/entitlement-management-logic-apps/extensibility-approver-experience.png":::
234
234
235
235
### Requestor experience
236
236
@@ -245,7 +245,8 @@ The following status updates are displayed to users based on their custom extens
245
245
|When the extension resumes | Process continues |
246
246
247
247
This is an example of a MyAccess request history from a requestor after the extension resumes:
248
-
:::image type="content" source="media/entitlement-management-logic-apps/extensibility-requestor-experience.png" alt-text="Screenshot of the requestor screen.":::
248
+
249
+
:::image type="content" source="media/entitlement-management-logic-apps/extensibility-requestor-experience.png" alt-text="Screenshot of the requestor screen." lightbox="media/entitlement-management-logic-apps/extensibility-requestor-experience.png":::
249
250
250
251
## Troubleshooting and Validation
251
252
@@ -266,4 +267,4 @@ To verify that your custom extension has correctly triggered the associated Logi
266
267
## Next steps
267
268
268
269
-[Delegation and roles in entitlement management](entitlement-management-delegate.md)
269
-
-[Create and manage a catalog of resources in entitlement management](entitlement-management-catalog-create.md)
270
+
-[Create and manage a catalog of resources in entitlement management](entitlement-management-catalog-create.md)
0 commit comments