### Example: Create Device Configuration Rule for No Users - PowerShell Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/admin/security-and-compliance/m365b-devices-basic-mobility-security-policies-configure.md An example demonstrating the creation of a device configuration rule that applies to no devices by using a null GUID for the target group. This rule is associated with the 'Contoso Engineering' policy. ```powershell New-DeviceConfigurationRule -Policy "Contoso Engineering" -TargetGroups "00000000-0000-0000-0000-000000000000" ``` -------------------------------- ### System Instructions Prompt Example for MCP Tools Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/admin/manage/mrc-mcp.md Use this system-level instruction prompt to encourage AI clients to utilize the Release Communications MCP Server tools for retrieving product release information. Ensure the prompt explicitly mentions the available tools. ```markdown You have access to MCP tools provided by the Release Communications MCP Server: - `get_recent_roadmaps` - `get_roadmap_by_id` - `get_recent_azure_updates` - `get_azure_update_by_id` When handling questions about Microsoft 365 Roadmap features or Azure service updates, use these tools to retrieve the most current and authoritative release information before responding. When handling questions about Microsoft 365 product roadmap timelines, upcoming feature releases, Azure service updates, or release status for specific products (Teams, Outlook, SharePoint, Excel, etc). ``` -------------------------------- ### Get User Data Filter Parameters Example (JSON) Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/copilot/employee-self-service/sap-employee-read-write-scenarios.md Example format for filter parameters used in the 'SuccessFactors System Get Common Execution' to retrieve user data. It demonstrates how to dynamically insert user context IDs into the filter string. ```json "{ \"personIdExternalVal\": \"" & Global.ESS_UserContext_Employee_Id & \"\",\"userIdVal\": \"" & Global.ESS_UserContext_User_Id & \"" }" ``` -------------------------------- ### Example Organization Relationship Update Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-multitenant-migration.md An example of updating an organization relationship, potentially for MTO setup or migration configuration. Note the inclusion of domain names and tenant IDs. ```powershell Set-OrganizationRelationship -Identity "MTO-OrgRel-ae2b6c6c-818a-4420-9830-c6083e37495e" -DomainNames "kingdomshu.onmicrosoft.com","ae2b6c6c-818a-4420-9830-c6083e37495e ``` -------------------------------- ### Infrastructure Setup for External System Integration Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/copilot/employee-self-service/sapsuccessfactors.md Guidance on configuring network and IP allowlisting for Power Platform environments to access external systems like SAP SuccessFactors. ```APIDOC ## Infrastructure Setup for External System Solution Integration **Description:** Enterprise organizations often secure third-party knowledge sources from external networks. When integrating these systems into the Employee Self-Service agent, they must be accessible to the Power Platform environment hosting the agent. **Requirements:** - Systems must be configured with allowlists for the source IP addresses of the Power Platform environment. - For SAP SuccessFactors (SF) integration using OData v2.0, allowlist Power Platform connectors to communicate with the SF endpoint. - For additional data security requirements, especially for OData exchange, consult with security specialists to harden data-in-transit security. **Resources:** - [Power Platform URLs and IP address ranges - Power Platform](/power-platform/admin/online-requirements) - [Managed connectors outbound IP addresses](/connectors/common/outbound-ip-addresses#power-platform) ``` -------------------------------- ### Get CTIM Request Status Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-identity-mapping.md Retrieves the status of a CTIM request, which should be 'Complete' before starting mailbox migration. ```PowerShell Get-CtimRequest -RequestId ``` -------------------------------- ### Get Security Group Guid Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-identity-mapping.md Retrieve the ExchangeObjectId for a distribution group to use as the SecurityGroupGuid when initiating a copy request. ```powershell Get-DistributionGroup -Identity "Group Name" | fl ExchangeObjectId ``` -------------------------------- ### Initiate Mapping Using CSV (Target Tenant) Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-multitenant-migration.md After uploading a manually populated CSV mapping file, run this command to initiate the mapping process. ```powershell New-CtimMapRequest -SourceTenantGuid -UseCsv ``` -------------------------------- ### Example CSV for Migration Batch Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-mailbox-migration.md A minimal example of a CSV file used for initiating migration batches. The 'EmailAddress' column should contain the primary SMTP address in the target tenant. ```CSV EmailAddress userA@northwindtraders.onmicrosoft.com userB@northwindtraders.onmicrosoft.com userC@northwindtraders.onmicrosoft.com ``` -------------------------------- ### Get Mailbox Permissions (Source Tenant) Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-mailbox-migration.md Example output of mailbox permissions before a move from the source tenant. This helps in verifying permissions prior to migration. ```PowerShell Get-MailboxPermission TestUser_7 | Format-Table -AutoSize User, AccessRights, is Inherited, Deny User AccessRights IsInherited Deny ---- ------------ ----------- ---- NT AUTHORITY\SELF {FullAccess, ReadPermission} False False TestUser_8@contoso.onmicrosoft.com {FullAccess} False False ``` -------------------------------- ### Retrieve all device policies Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/admin/security-and-compliance/m365b-devices-basic-mobility-security-policies-configure.md Demonstrates how to use the Get-DevicePolicy cmdlet to list both device configuration policies and device conditional access policies. ```PowerShell Get-DevicePolicy ``` -------------------------------- ### Example Baseline File Naming Conventions Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/performance-tuning-using-baselines-and-history.md Use a consistent naming convention for baseline files that includes date, time, test description, tool used, and performance outcome. This aids in later troubleshooting by allowing easy comparison of different performance states. ```text Feb_09_2015_9amPST_PerfBaseline_Netmon_ClientToEgress_Normal ``` ```text Jan_10_2015_3pmCST_PerfBaseline_PsPing_ClientToO365_bypassProxy_SLOW ``` ```text Feb_08_2015_2pmEST_PerfBaseline_BADPerf ``` ```text Feb_08_2015_8-30amEST_PerfBaseline_GoodPerf ``` -------------------------------- ### Get Mailbox Permissions (Target Tenant) Source: https://github.com/microsoftdocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/cross-tenant-mailbox-migration.md Example output of mailbox permissions after the move to the target tenant. This verifies that permissions are correctly set up in the new environment. ```PowerShell Get-MailboxPermission TestUser_7 | Format-Table -AutoSize User, AccessRights, IsInherited, Deny User AccessRights IsInherited Deny ---- ------------ ----------- ---- NT AUTHORITY\SELF {FullAccess, ReadPermission} False False TestUser_8@northwindtraders.onmicrosoft.com {FullAccess} False False ```