Skip to content

Commit f630caa

Browse files
committed
Merge branch 'owinfreyATL-TriggerLogicApps-EntitlementManagement' of https://github.com/OWinfreyATL/azure-docs-pr into owinfreyATL-TriggerLogicApps-EntitlementManagement
2 parents afcb7e9 + 3c97bd1 commit f630caa

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/active-directory/governance/entitlement-management-logic-apps-integration.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ These triggers to Logic Apps are controlled in a tab within access package polic
8181
:::image type="content" source="media/entitlement-management-logic-apps/create-logic-app-extension-details.png" alt-text="Screenshot of creating logic app detail selections.":::
8282

8383
> [!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.
8585
8686
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**.
8787

@@ -94,7 +94,7 @@ These triggers to Logic Apps are controlled in a tab within access package polic
9494
1. Navigate to the Custom Extensions tab within a Catalog as mentioned earlier.
9595

9696
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":::
9898
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*”.
9999

100100
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”.
@@ -175,7 +175,7 @@ Microsoft.graph.accessPackageCustomExtensionStage.assignmentRequestRemoved
175175
``
176176

177177
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":::
179179

180180
An example of a resume request payload is:
181181

@@ -230,7 +230,7 @@ Content-Type: application/json
230230
### Approver experience
231231

232232
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":::
234234

235235
### Requestor experience
236236

@@ -245,7 +245,8 @@ The following status updates are displayed to users based on their custom extens
245245
|When the extension resumes | Process continues |
246246

247247
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":::
249250

250251
## Troubleshooting and Validation
251252

@@ -266,4 +267,4 @@ To verify that your custom extension has correctly triggered the associated Logi
266267
## Next steps
267268

268269
- [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

Comments
 (0)