Skip to content

Commit c907e42

Browse files
committed
update to user mapping docs
1 parent d12cd16 commit c907e42

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/transform/modernize-userinterface-site-pages-usermapping.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: User mapping during page transformation
33
description: Explains how to the user mapping works when transforming pages
4-
ms.date: 11/04/2019
4+
ms.date: 11/08/2019
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
@@ -30,12 +30,13 @@ sharepoint\system,[email protected]
3030
contoso\paul,[email protected]
3131
contoso\bert,[email protected]
3232
s-1-5-21-3138640143-967965215-2549001177-3604,SalesGroup
33+
s-1-5-21-2364077317-3999105188-691961326-1128,c:0t.c|tenant|b0f984d9-e9d5-432a-bec9-896f910254ba
3334
```
3435

3536
Some things to note:
3637

3738
- You can map the **system account** via sharepoint\system
38-
- Groups have to be specified via the group sid
39+
- Groups have to be specified via the group sid as source. Group targets can be specified by Azure AD group name but it's better to unique identify them via using the Azure AD group id like shown in c:0t.c|tenant|b0f984d9-e9d5-432a-bec9-896f910254ba
3940

4041
Creating the mapping file is the first step, to actually use it you need to specify the file via the `UserMappingFile` parameter to the `ConvertTo-PnPClientSidePage` cmdlet if you're using PnP PowerShell. If you're using .Net then you can specify the file via the `UserMappingFile` attribute of the .Net page transformation configuration objects (`PageTransformationInformation` and `PublishingPageTransformationInformation`).
4142

0 commit comments

Comments
 (0)