Skip to content

Commit ba35e95

Browse files
update doc timestamp in frontmatter & fix mardown errors
1 parent cc5eb6b commit ba35e95

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Replace an expiring client secret in a SharePoint Add-in
33
description: Add a new client secret for a SharePoint Add-in that is registered with AppRegNew.aspx.
4-
ms.date: 06/22/2021
4+
ms.date: 03/03/2022
55
ms.prod: sharepoint
66
ms.localizationpriority: high
77
---
@@ -14,10 +14,12 @@ Client secrets for SharePoint Add-ins that are registered by using the AppRegNew
1414
> This article is about SharePoint Add-ins that are distributed through an organization catalog and registered with the AppRegNew.aspx page. If the add-in is registered on the Seller Dashboard, see [Create or update client IDs and secrets in the Seller Dashboard](/office/dev/store/create-or-update-client-ids-and-secrets).
1515
1616
## Recommended maintenance schedule
17+
1718
We recommend to create new secrets a minimum of 30 days before they expire. This gives you a month of time before the old credentials expire.
19+
1820
We recommend to only remove secrets a minimum of 7 days after expiration, provided you have removed them from the application configuration.
19-
Removing an expired secret from ACS before you remove it from the application configuration will cause errors.
2021

22+
Removing an expired secret from ACS before you remove it from the application configuration will cause errors.
2123

2224
## Prerequisites
2325

0 commit comments

Comments
 (0)