Skip to content

Commit 441c10a

Browse files
authored
Merge branch 'main' into cmcatee-pay-by-wire-transfer
2 parents 4a9745e + a434c5a commit 441c10a

2 files changed

Lines changed: 3 additions & 1 deletion

File tree

microsoft-365/admin/misc/password-policy-recommendations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Good password practices fall into a few broad categories:
6262

6363
The primary goal of a more secure password system is password diversity. You want your password policy to contain lots of different and hard to guess passwords. Here are a few recommendations for keeping your organization as secure as possible.
6464

65-
- Maintain an fourteen-character minimum length requirement
65+
- Maintain a fourteen-character minimum length requirement
6666

6767
- Don't require character composition requirements. For example, \*&(^%$
6868

microsoft-365/documentprocessing/esignature-setup.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -190,4 +190,6 @@ At the end of the signing process when all required parties have signed, a copy
190190
![Screenshot showing a signed document in a provider-specific folder.](../media/content-understanding/esignature-other-provider-folder.png)
191191

192192
> [!NOTE]
193+
> Starting September 2025 and rolling out through November 2025, signed documents will be automatically saved back to the original folder (the same location where the original document was stored when the e-signature request was initiated). This replaces the previously used dedicated file structure in which signed documents were stored in a separate, dedicated structure as described above.
194+
193195
> How long a copy of the signed document is retained in the other provider's platform depends solely on your document storage and retention policy settings for that provider service.

0 commit comments

Comments
 (0)