Skip to content

Commit 26da511

Browse files
Update articles/security/fundamentals/customer-lockbox-overview.md
Co-authored-by: Diana Richards <[email protected]>
1 parent 58d3347 commit 26da511

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/security/fundamentals/customer-lockbox-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ The following steps outline a typical workflow for a Customer Lockbox for Micros
9595

9696

9797
Example email:
98-
:::image type="content" source="./media/customer-lockbox-overview/customer-lockbox-email-notification.png" lightbox="./media/customer-lockbox-overview/customer-lockbox-email-notification.png" alt-text="A screesnhot the the email notification .":::
98+
:::image type="content" source="./media/customer-lockbox-overview/customer-lockbox-email-notification.png" lightbox="./media/customer-lockbox-overview/customer-lockbox-email-notification.png" alt-text="A screenshot of the email notification.":::
9999

100100
1. The email notification provides a link to the **Customer Lockbox** blade in the Administration module. The designated approver signs in to the Azure portal to view any pending requests that their organization has for Customer Lockbox for Microsoft Azure:
101101
:::image type="content" source="./media/customer-lockbox-overview/customer-lockbox-landing-page.png" lightbox="./media/customer-lockbox-overview/customer-lockbox-landing-page.png" alt-text="A screenshot of the Customer Lockbox for Microsoft Azure landing page.":::

0 commit comments

Comments
 (0)