Skip to content

Commit f7cceb0

Browse files
Merge pull request SharePoint#7776 from westleyMS/patch-16
Update replace-an-expiring-client-secret-in-a-sharepoint-add-in.md
2 parents d4ce33d + ba35e95 commit f7cceb0

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

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

Lines changed: 9 additions & 1 deletion
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
---
@@ -13,6 +13,14 @@ Client secrets for SharePoint Add-ins that are registered by using the AppRegNew
1313
> [!NOTE]
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
16+
## Recommended maintenance schedule
17+
18+
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+
20+
We recommend to only remove secrets a minimum of 7 days after expiration, provided you have removed them from the application configuration.
21+
22+
Removing an expired secret from ACS before you remove it from the application configuration will cause errors.
23+
1624
## Prerequisites
1725

1826
Ensure the following before you begin:

0 commit comments

Comments
 (0)