Skip to content

Commit daab73a

Browse files
authored
Update policy-keys-overview.md
1 parent db7b604 commit daab73a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/active-directory-b2c/policy-keys-overview.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,9 +79,11 @@ If an Azure AD B2C keyset has multiple keys, only one of the keys is active at a
7979

8080
## Key caching
8181

82-
When a key is uploaded, the activation flag on the key is set to false by default. The new key will then be updated on all nodes. Only when the new key has been updated on all cache nodes will the activation flag set to true.  
82+
When a key is uploaded, the activation flag on the key is set to false by default. You can then set the state of this key to **Enabled**. If a key enabled and valid (current time is between NBF and EXP), then the key will be used.
8383

84-
The activation flag property is modifiable within the Azure Portal UX allowing admins to disable a key and take it out of rotation. An active key can be an expired key. 
84+
### Key state
85+
86+
The activation flag property is modifiable within the Azure Portal UX allowing admins to disable a key and take it out of rotation.
8587

8688
## Policy key management
8789

0 commit comments

Comments
 (0)