Merge pull request #10390 from MicrosoftDocs/chrisda

Update Remove-UserPhoto.md

Author: chrisda

exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md

@@ -81,6 +81,10 @@ The Entries parameter specifies the values that you want to add to the Tenant Al
 
 To enter multiple values, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
+For senders, files, and URLs the maximum number of allow entries for each type is 500, and the maximum number of block entries for each type is 500 (1000 entries total for each type).
+
+The maximum number of characters in a file entry is 64 and the maximum number of characters in a URL entry is 250.
+
 You can't mix value types (file, sender, or URL) or allow and block actions in the same command.
 
 In most cases, you can't modify the URL, file, or sender values after you create the entry. The only exception is allow URL entries for phishing simulations (ListType = URL, ListSubType = AdvancedDelivery).

exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md

@@ -64,7 +64,7 @@ Accept wildcard characters: False
 The SendingInfrastructure parameter specifies the source of the messages sent by the spoofed sender that's defined in the SpoofedUser parameter. Valid values are:
 
 - An email domain (for example contoso.com). The domain is found in the reverse DNS lookup (PTR record) of the source email server's IP address.
-- An IP address using the syntax: \<source IP\>/24 (for example, 192.168.100.100/24). Use the IP address if the source IP address has no PTR record.
+- An IP address using the syntax: \<source IP\>/24 (for example, 192.168.100.100/24). Use the IP address if the source IP address has no PTR record. /24 is the only available and maximum subnet depth.
 - A verified DKIM domain.
 
 ```yaml
@@ -86,6 +86,8 @@ The SpoofedUser parameter specifies the email address or domain for the spoofed
 - For domains outside your organization (cross-org), use the domain of the email address that appears in the From field of the message.
 - For domains inside your organization (intra-org), use the full email address that appears in the From field of the message.
 
+For spoofed senders, the maximum number of entries is 1024.
+
 ```yaml
 Type: String
 Parameter Sets: (All)

exchange/exchange-ps/exchange/Remove-UserPhoto.md

@@ -50,7 +50,7 @@ In on-premises Exchange, it also removes the user's photo from their Active Dire
 **Notes**:
 
 - Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image.
-- **Note**: In Microsoft Graph, the [Remove-MgUserPhoto](https://learn.microsoft.com/powershell/module/microsoft.graph.users/remove-mguserphoto) and [Update-MgUserPhoto](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguserphoto) cmdlets are also available.
+- In Microsoft Graph, the [Update-MgUserPhoto](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguserphoto) cmdlet is also available.
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).