MicrosoftPlaces.dll-Help.xml
|
<?xml version="1.0" encoding="utf-8"?>
<helpItems schema="maml" xmlns="http://msh"> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp"> <command:details> <command:name>Connect-MicrosoftPlaces</command:name> <command:verb>Connect</command:verb> <command:noun>MicrosoftPlaces</command:noun> <maml:description> <maml:para>You can connect to Places PowerShell using modern authentication by running the Connect-MicrosoftPlaces cmdlet. This cmdlet works for accounts with or without multifactor authentication (MFA).</maml:para> </maml:description> </command:details> <maml:description> <maml:para>This command creates a PowerShell connection to enable the use of other MicrosoftPlaces PowerShell commands.</maml:para> </maml:description> <command:syntax> <command:syntaxItem> <maml:name>Connect-MicrosoftPlaces</maml:name> </command:syntaxItem> </command:syntax> <command:parameters /> <command:inputTypes /> <command:returnValues /> <maml:alertSet> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <command:examples> <command:example> <maml:title>-------------------------- Example 1 --------------------------</maml:title> <dev:code>Connect-MicrosoftPlaces</dev:code> <dev:remarks> <maml:para>This example connects to Microsoft Places. A browser window opens where you enter the identity and authentication credentials.</maml:para> </dev:remarks> </command:example> </command:examples> <command:relatedLinks> <maml:navigationLink> <maml:linkText>Online Version:</maml:linkText> <maml:uri>https://learn.microsoft.com/en-us/microsoft-365/places/powershell/connect-microsoftplaces</maml:uri> </maml:navigationLink> </command:relatedLinks> </command:command> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp"> <command:details> <command:name>New-Place</command:name> <command:verb>New</command:verb> <command:noun>Place</command:noun> <maml:description> <maml:para>Use the New-Place cmdlet to create buildings, floors, sections or desks within your Places directory.</maml:para> </maml:description> </command:details> <maml:description> <maml:para>This command creates a new Place of type Building, Floor, Section or Desk in your Places Directory.</maml:para> </maml:description> <command:syntax> <command:syntaxItem> <maml:name>New-Place</maml:name> </command:syntaxItem> </command:syntax> <command:parameters> <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="true" position="0" aliases="none"> <maml:name>DisplayName</maml:name> <maml:description> <maml:para>The DisplayName parameter specifies the display name of the place. The maximum length is 200 characters.</maml:para> <maml:para>A building's display name is visible:</maml:para> <maml:para>- In Outlook, when users are setting up their work hours and location, they're able to select a building.</maml:para> <maml:para>- In Places Explore page that shows who else is in the same building, nearby buildings, and more.</maml:para> <maml:para>- In Places Finder, as a filter when searching for a conference room or workspace.</maml:para> <maml:para>A floor's display name is visible in Places Finder as a filter when searching for a conference room or workspace.4</maml:para> </maml:description> <command:parameterValue required="true" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="true" position="1" aliases="none"> <maml:name>Type</maml:name> <maml:description> <maml:para>The Type parameter specifies the type of the place that is being created. Valid values are:</maml:para> <maml:para>- Building</maml:para> <maml:para>- Floor</maml:para> <maml:para>- Section</maml:para> <maml:para>- Desk</maml:para> </maml:description> <command:parameterValue required="true" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="2" aliases="none"> <maml:name>City</maml:name> <maml:description> <maml:para>The City parameter specifies the room's city. If the value contains spaces, enclose the value in quotation marks ("). The maximum length is 200 characters.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="3" aliases="none"> <maml:name>CountryOrRegion</maml:name> <maml:description> <maml:para>The CountryOrRegion parameter specifies the room's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name).</maml:para> <maml:para>A reference for two-letter country codes is available at Country Codes List (https://www.nationsonline.org/oneworld/country_code_list.htm).</maml:para> <maml:para>Address information is used by the Places Explore page to show nearby buildings.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="4" aliases="none"> <maml:name>Label</maml:name> <maml:description> <maml:para>The Label parameter specifies a descriptive label for the place. If the value contains spaces, enclose the value in quotation marks ("). The maximum length is 200 characters.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="5" aliases="none"> <maml:name>GeoCoordinates</maml:name> <maml:description> <maml:para>The GeoCoordinates parameter specifies the building's location in latitude, longitude, and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats.</maml:para> <maml:para>- Latitude and longitude: For example, "47.644125;-122.122411"</maml:para> <maml:para>- Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432"</maml:para> <maml:para>Note: If period separators don't work for you, use commas instead.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">GeoCoordinates</command:parameterValue> <dev:type> <maml:name>GeoCoordinates</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="6" aliases="none"> <maml:name>ParentId</maml:name> <maml:description> <maml:para>The ParentId parameter specifies the ID of a Place in the parent location hierarchy in Microsoft Places. </maml:para> <maml:para>- A room should have a parent floor or section.</maml:para> <maml:para>- A workspace or desk should have a parent section.</maml:para> <maml:para>- A section should have a parent floor.</maml:para> <maml:para>- A floor should have a parent building.</maml:para> <maml:para>Once the ParentId is set for a room or workspace, legacy room/workspace properties that are actually about the floor (such as floor number) or about the building (such as address and location information) become read-only for that room/workspace using Set-PlaceV3. The same properties can be updated by updating the Floor or Building directly using Set-PlaceV3.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="7" aliases="none"> <maml:name>PostalCode</maml:name> <maml:description> <maml:para>The PostalCode parameter specifies the room's postal code. The maximum length is 200 characters.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="8" aliases="none"> <maml:name>ResourceLinks</maml:name> <maml:description> <maml:para>The ResourceLinks parameter specifies external links or Teams app IDs that should be associated with this building, such as a dining menu, a link to services or a Teams app for visitor management. For more information on how to set up services in Places, see Services in Places.</maml:para> <maml:para>The value must be provided as an array of links, as shown in Example 4. Each link should contain the following properties: Name, Value, and Type. For example, a link would be written as @{name="TestLink"; value="https://contoso.com/"; type="Url"}.</maml:para> <maml:para>- Name: This string will be used to show how your link or app name will be displayed in the Places app. The maximum length is 200 characters.</maml:para> <maml:para>- Value: This value should be either a url link or a Teams app ID. Teams app IDs can be found in the App Details page of the app in the Manage apps page in Teams admin center. The maximum length is 1000 characters.</maml:para> <maml:para>- Type must be one of the supported types:</maml:para> <maml:para> - Url: indicates that this is a url link.</maml:para> <maml:para> - MetaOsApp: indicates that this link is a Teams app.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">ResourceLink[]</command:parameterValue> <dev:type> <maml:name>ResourceLink[]</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="9" aliases="none"> <maml:name>SortOrder</maml:name> <maml:description> <maml:para>The SortOrder parameter specifies the sort order of the floor. For example, a floor might be named "Lobby" with a sort order of 0 to show this floor first in ordered lists.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="10" aliases="none"> <maml:name>State</maml:name> <maml:description> <maml:para>The State parameter specifies the room's state or province. The maximum length is 200 characters.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="11" aliases="none"> <maml:name>Street</maml:name> <maml:description> <maml:para>The Street parameter specifies the room's physical address. The maximum length is 200 characters.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="12" aliases="none"> <maml:name>Tags</maml:name> <maml:description> <maml:para>The Tags parameter specifies other features of the room (for example, details like the type of view or furniture type). There's no maximum length currently.</maml:para> <maml:para>You can specify multiple labels separated by commas. If the labels contains spaces, enclose the values in quotation marks: "Label 1","Label 2",..."Label N".</maml:para> <maml:para>Note: The entire set is replaced on update. To add or remove a value, be sure to include previous values that should be persisted.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String[]</command:parameterValue> <dev:type> <maml:name>String[]</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <maml:alertSet> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <command:examples> <command:example> <maml:title>-------------------------- Example 1 --------------------------</maml:title> <dev:code>New-Place -Type Building -Name 'Building 3'</dev:code> <dev:code> New-Place -Type Floor -Name 'Lobby' -ParentId f12172b6-195d-4e6e-8f4f-eb72e41de99a</dev:code> <dev:remarks> <maml:para>This example creates a new building and a floor within that building.</maml:para> <maml:para>After Building 3 is created successfully, read its PlaceId to use when setting the ParentId on the floors.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 2 --------------------------</maml:title> <dev:code>New-Place -Name 'Building 3' -Type Building -Description 'Building 3 in North of Redmond Campus' -CountryOrRegion US -State WA -City Redmond -Street 'Street 3' -PostalCode 98052</dev:code> <dev:remarks> <maml:para>This example creates a new building with address information.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 3 --------------------------</maml:title> <dev:code> New-Place -Name 'Building 3' -Type Building -ResourceLinks @{name="TestLink";value="https://contoso.com/";type="Url"}'</dev:code> <dev:remarks> <maml:para>This example creates a new building with resource links.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 4 --------------------------</maml:title> <dev:code> $mbx = New-Mailbox -Room 'DeskMailboxName' Set-Mailbox $mbx.Identity -Type Desk -HiddenFromAddressListsEnabled $true $section = New-Place -Name 'Section1' -Type Section -ParentId 'someFloorId' New-Place -Name 'Desk101' -Type Desk -ParentId $section.PlaceId -Mailbox $mbx.ExternalDirectoryObjectId </dev:code> <dev:remarks> <maml:para>This examples creates section parented to a floor and then a desk mailbox and assigns it to an existing desk entity. Please note that you need to have installed `ExchangeOnlineManagement` module and ran the `Connect-ExchangeOnline` cmdlet before running the following:</maml:para> </dev:remarks> </command:example> </command:examples> <command:relatedLinks> <maml:navigationLink> <maml:linkText>Online Version:</maml:linkText> <maml:uri>https://learn.microsoft.com/en-us/microsoft-365/places/powershell/new-place</maml:uri> </maml:navigationLink> </command:relatedLinks> </command:command> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp"> <command:details> <command:name>Get-PlaceV3</command:name> <command:verb>Get</command:verb> <command:noun>PlaceV3</command:noun> <maml:description> <maml:para>Use the Get-PlaceV3 cmdlet to view metadata configured on conference rooms, workspaces, buildings, floors, sections, or desks within the Places directory.</maml:para> </maml:description> </command:details> <maml:description> <maml:para>You need to be assigned permissions before you can run this cmdlet. You must have either the Exchange Admin role or the Places TenantPlacesManagement role.</maml:para> </maml:description> <command:syntax> <command:syntaxItem> <maml:name>Get-PlaceV3</maml:name> </command:syntaxItem> </command:syntax> <command:parameters> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="true" position="0" aliases="none"> <maml:name>Identity</maml:name> <maml:description> <maml:para>The identity parameter specifies the place that you want to view. You can use any value that uniquely identifies a place.</maml:para> <maml:para>For example, for places based on a mailbox (conference rooms and workspaces):</maml:para> <maml:para>- Name</maml:para> <maml:para>- Alias</maml:para> <maml:para>- Distinguished name (DN)</maml:para> <maml:para>- Canonical DN</maml:para> <maml:para>- Email address</maml:para> <maml:para>- GUID</maml:para> <maml:para>For example, for places that aren't based on a mailbox (buildings, floors, sections or desks):</maml:para> <maml:para>- Name_PlaceId</maml:para> <maml:para>- PlaceId</maml:para> <maml:para>You can't use this parameter with the Type parameter.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="1" aliases="none"> <maml:name>Type</maml:name> <maml:description> <maml:para>The Type parameter specifies the type of the place that you want to view. Valid values are:</maml:para> <maml:para>- Room</maml:para> <maml:para>- Roomlist</maml:para> <maml:para>- Space</maml:para> <maml:para>- Building</maml:para> <maml:para>- Floor</maml:para> <maml:para>- Section</maml:para> <maml:para>- Desk</maml:para> <maml:para>You can't use this parameter with the Identity parameter.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="2" aliases="none"> <maml:name>AncestorId</maml:name> <maml:description> <maml:para>The AncestorId parameter specifies the guid of place. If the specified place found, it returns all places below this place in the directory hierarchy. For example, if a building's PlaceId is provided as the AncestorId, the command would return all floors, rooms, and workspaces that are under that building in the directory hierarchy.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <maml:alertSet> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <command:examples> <command:example> <maml:title>-------------------------- Example 1 --------------------------</maml:title> <dev:code>Get-PlaceV3 -Identity smtp@domain.com</dev:code> <dev:remarks> <maml:para>This example returns a room or workspace using its smtp address identifier.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 2 --------------------------</maml:title> <dev:code>Get-PlaceV3 -Type Building</dev:code> <dev:remarks> <maml:para>This example returns all places of a certain type.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 3 --------------------------</maml:title> <dev:code>Get-PlaceV3 -Type Building | Where-Object -Property DisplayName -eq 'Pine Valley' | fl PlaceId</dev:code> <dev:remarks> <maml:para>This example returns the PlaceId based on a place's name and type.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 4 --------------------------</maml:title> <dev:code>Get-PlaceV3 -AncestorId 86897e93-bcef-4c05-af9d-45116dda791f</dev:code> <dev:remarks> <maml:para>This example returns all places whose ancestor is a specific place.</maml:para> </dev:remarks> </command:example> </command:examples> <command:relatedLinks> <maml:navigationLink> <maml:linkText>Online Version:</maml:linkText> <maml:uri>https://learn.microsoft.com/en-us/microsoft-365/places/powershell/get-placev3</maml:uri> </maml:navigationLink> </command:relatedLinks> </command:command> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp"> <command:details> <command:name>Set-PlaceV3</command:name> <command:verb>Set</command:verb> <command:noun>PlaceV3</command:noun> <maml:description> <maml:para>Use the Set-PlaceV3 cmdlet to update metadata about your rooms, workspaces, floors, or buildings within your Places directory. .</maml:para> </maml:description> </command:details> <maml:description> <maml:para>Updates to conference rooms and workspaces can take up to 24 hours to reflect. We are working on eliminating this delay. If you are bulk onboarding conference rooms and workspaces to Places, we recommend leveraging `Initialize-Places` cmdlet, which is able to force the changes to reflect immediately.</maml:para> <maml:para>You need to be assigned permissions before you can run this cmdlet. You must have either the Exchange Admin role or the Places TenantPlacesManagement role.</maml:para> </maml:description> <command:syntax> <command:syntaxItem> <maml:name>Set-PlaceV3</maml:name> </command:syntaxItem> </command:syntax> <command:parameters> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="true" position="0" aliases="none"> <maml:name>Identity</maml:name> <maml:description> <maml:para>The identity parameter specifies the place that you want to update. You can use any value that uniquely identifies a place.</maml:para> <maml:para>For example, for places based on a mailbox (conference rooms and workspaces):</maml:para> <maml:para>- Name</maml:para> <maml:para>- Alias</maml:para> <maml:para>- Distinguished name (DN)</maml:para> <maml:para>- Canonical DN</maml:para> <maml:para>- Email address</maml:para> <maml:para>- GUID</maml:para> <maml:para>For example, for places that aren't based on a mailbox (buildings, floors, sections or desks):</maml:para> <maml:para>- Name_PlaceId</maml:para> <maml:para>- PlaceId</maml:para> <maml:para>You can't use this parameter with the Type parameter.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="1" aliases="none"> <maml:name>AudioDeviceName</maml:name> <maml:description> <maml:para>The AudioDeviceName parameter specifies the name of the audio device in the room. If the value contains spaces, enclose the value in quotation marks (").</maml:para> <maml:para>The default value is blank ($null). To indicate that this room has no audio device, use the value $null for this parameter.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="2" aliases="none"> <maml:name>Building</maml:name> <maml:description> <maml:para>Note: Building parameter is deprecated and provided here for backward compatibility only. Building information will be read from the Building entity that's on the parent chain of the room/workspace.</maml:para> <maml:para>The Building parameter specifies the building name or building number that the room is in. If the value contains spaces, enclose the value in quotation marks (").</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="3" aliases="none"> <maml:name>Capacity</maml:name> <maml:description> <maml:para>The Capacity parameter specifies the capacity of the room. A valid value is an integer.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">System.Int32</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="4" aliases="none"> <maml:name>City</maml:name> <maml:description> <maml:para>The City parameter specifies the building's city. If the value contains spaces, enclose the value in quotation marks ("). The maximum length is 200 characters.</maml:para> <maml:para>We recommend managing the location data on the Building rather than the Room/Workspace. There's a hierarchy between rooms -> floors -> buildings, and rooms inherit the location attributes of their Building.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="5" aliases="none"> <maml:name>CountryOrRegion</maml:name> <maml:description> <maml:para>The CountryOrRegion parameter specifies the building's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name).</maml:para> <maml:para>A reference for two-letter country codes is available at Country Codes List (https://www.nationsonline.org/oneworld/country_code_list.htm).</maml:para> <maml:para>We recommend managing the location data on the Building rather than the Room/Workspace. There's a hierarchy between rooms -> floors -> buildings, and rooms inherit the location attributes of their Building.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="6" aliases="none"> <maml:name>Label</maml:name> <maml:description> <maml:para>The Label parameter specifies a descriptive label for the place. If the value contains spaces, enclose the value in quotation marks ("). The maximum length is 200 characters.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="7" aliases="none"> <maml:name>DisplayDeviceName</maml:name> <maml:description> <maml:para>The DisplayDeviceName parameter specifies the name of the display device in the room. If the value contains spaces, enclose the value in quotation marks (").</maml:para> <maml:para>The default value is blank ($null). To indicate that this room has no display device, use the value $null for this parameter.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="8" aliases="none"> <maml:name>FloorLabel</maml:name> <maml:description> <maml:para>Note: FloorLabel parameter is deprecated in Places and provided here for backward compatibility with Outlook Roomfinder only. Floor information in Places will be read from the Floor entity that's on the parent chain of the room/workspace. However, Outlook Roomfinder still continues to use FloorLabel.</maml:para> <maml:para>The FloorLabel parameter specifies a descriptive label for the floor. If the value contains spaces, enclose the value in quotation marks (").</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="9" aliases="none"> <maml:name>Floor</maml:name> <maml:description> <maml:para>Note: Floor parameter is deprecated in Places and provided here for backward compatibility with Outlook Roomfinder only. Floor information in Places will be read from the Floor entity that's on the parent chain of the room/workspace. However, Outlook Roomfinder still continues to use Floor.</maml:para> <maml:para>The Floor parameter specifies the sort order of the floor within a particular building. </maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="10" aliases="none"> <maml:name>GeoCoordinates</maml:name> <maml:description> <maml:para>The GeoCoordinates parameter specifies the building's location in latitude, longitude, and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats.</maml:para> <maml:para>- Latitude and longitude: For example, "47.644125;-122.122411"</maml:para> <maml:para>- Latitude, longitude, and altitude: For example, "47.644125;-122.122411;161.432"</maml:para> <maml:para>Note: If period separators don't work for you, use commas instead.</maml:para> <maml:para>We recommend managing the location data on the Building rather than the Room/Workspace. There's a hierarchy between rooms -> floors -> buildings, and room's will inherit the location attributes of their Building.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">GeoCoordinates</command:parameterValue> <dev:type> <maml:name>GeoCoordinates</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="11" aliases="none"> <maml:name>IsWheelChairAccessible</maml:name> <maml:description> <maml:para>The IsWheelChairAccessible parameter specifies whether the place is wheelchair accessible. Valid values are:</maml:para> <maml:para>- $true: The place is wheelchair accessible.</maml:para> <maml:para>- $false: The place isn't wheelchair accessible. This is the default value.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">Boolean</command:parameterValue> <dev:type> <maml:name>Boolean</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="12" aliases="none"> <maml:name>MTREnabled</maml:name> <maml:description> <maml:para>The MTREnabled parameter identifies the room as configured with a Microsoft Teams room system. You can add Teams room systems as audio sources in Teams meetings that involve the room. Valid values are:</maml:para> <maml:para>- $true: The room has a Teams room system. You can add the Teams room system to Microsoft Teams meetings when selecting to join a meeting with room audio.</maml:para> <maml:para>- $false: The room doesn't have a Teams room system. Users can join Teams meetings using their PC or mobile device audio instead of using room audio. This is the default value.</maml:para> <maml:para>For more information about Microsoft Teams Rooms, see Microsoft Teams Rooms (https://learn.microsoft.com/en-us/microsoftteams/rooms/).</maml:para> <maml:para>Note: Currently, this parameter is informational only and results in no additional functionality.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">Boolean</command:parameterValue> <dev:type> <maml:name>Boolean</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="13" aliases="Name"> <maml:name>DisplayName</maml:name> <maml:description> <maml:para>The DisplayName parameter specifies the display name of the place. The maximum length is 200 characters. Set-PlaceV3 can only update the name of places that don't have an associated SMTP address, such as buildings and floors. To update the display name of a place that has an associated SMTP address such as conference rooms and workspaces, use the [Exchange Set-Mailbox cmdlet](/powershell/module/exchange/set-mailbox).</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="14" aliases="none"> <maml:name>ParentId</maml:name> <maml:description> <maml:para>The ParentId parameter specifies the ID of a Place in the parent location hierarchy in Microsoft Places. A room should have a parent floor or section. A workspace or desk should have a parent section. A section should have a parent floor. A floor should have a parent building.</maml:para> <maml:para>Once the ParentID is set to a room or workspace, some parameters that are actually about the floor (for example, FloorLabel) or about the building (for example, address and location information) will be read-only for that room/workspace using Set-Place V3. The same properties can be updated by updating the Floor or Building directly using Set-PlaceV3.</maml:para> <maml:para>Important: It is only recommended to use Set-PlaceV3 to add a ParentId. Once a ParentId has been set, do not change the ParentId. The Set-PlaceV3 cmdlet currently allows changing of ParentId, but this will result in directory hierarchy issues.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="15" aliases="none"> <maml:name>PostalCode</maml:name> <maml:description> <maml:para>The PostalCode parameter specifies the room's postal code.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="16" aliases="none"> <maml:name>ResourceLinks</maml:name> <maml:description> <maml:para>The ResourceLinks parameter specifies external links or Teams app IDs that should be associated with this building, such as a dining menu, a link to services or a Teams app for visitor management. For more information on how to set up services in Places, see Services in Places.</maml:para> <maml:para>The value must be provided as an array of links, as shown in Example 4. Each link should contain the following properties: Name, Value, and Type. For example, a link would be written as @{name="TestLink"; value="https://contoso.com/"; type="Url"}.</maml:para> <maml:para>- Name: This string will be used to show how your link or app name will be displayed in the Places app. The maximum length is 200 characters.</maml:para> <maml:para>- Value: This value should be either a url link or a Teams app ID. Teams app IDs can be found in the App Details page of the app in the Manage apps page in Teams admin center. The maximum length is 1000 characters.</maml:para> <maml:para>- Type must be one of the supported types:</maml:para> <maml:para> - Url: indicates that this is a url link.</maml:para> <maml:para> - MetaOsApp: indicates that this link is a Teams app.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">Link[]</command:parameterValue> <dev:type> <maml:name>Link[]</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="17" aliases="none"> <maml:name>SortOrder</maml:name> <maml:description> <maml:para>The SortOrder parameter specifies the sort order of the floor. For example, a floor might be named "Lobby" with a sort order of 0 to show this floor first in ordered lists.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">System.Int32</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="18" aliases="none"> <maml:name>State</maml:name> <maml:description> <maml:para>The State parameter specifies the room's state or province. The maximum length is 200 characters.</maml:para> <maml:para>We recommend managing the location data on the Building rather than the Room/Workspace. There's a hierarchy between rooms -> floors -> buildings, and room inherits the location attributes of their Building.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="19" aliases="none"> <maml:name>Street</maml:name> <maml:description> <maml:para>The Street parameter specifies the room's physical address. The maximum length is 200 characters.</maml:para> <maml:para>We recommend managing the location data on the Building rather than the Room/Workspace. There's a hierarchy between rooms -> floors -> buildings, and rooms inherit the location attributes of their Building.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="20" aliases="none"> <maml:name>Tags</maml:name> <maml:description> <maml:para>The Tags parameter specifies other features of the room (for example, details like the type of view or furniture type). There's no maximum length currently.</maml:para> <maml:para>You can specify multiple labels separated by commas. If the labels contains spaces, enclose the values in quotation marks: "Label 1","Label 2",..."Label N".</maml:para> <maml:para>Note: The entire set is replaced on update. To add or remove a value, be sure to include previous values that should be persisted.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String[]</command:parameterValue> <dev:type> <maml:name>String[]</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <maml:alertSet> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <command:examples> <command:example> <maml:title>-------------------------- Example 1 --------------------------</maml:title> <dev:code>Set-PlaceV3 -Identity 'room@contoso.com' -ParentId f12172b6-195d-4e6e-8f4f-eb72e41de99a</dev:code> <dev:code>Set-PlaceV3 -Identity f12172b6-195d-4e6e-8f4f-eb72e41de99a -ParentId daa2f89b-75c4-4eb7-adcc-ff249233338d</dev:code> <dev:remarks> <maml:para>This example sets up the directory hierarchy for a room, floor, and building.</maml:para> <maml:para>In this example, the floor's PlaceId is f12172b6-195d-4e6e-8f4f-eb72e41de99a, and the building's PlaceId is daa2f89b-75c4-4eb7-adcc-ff249233338d.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 2 --------------------------</maml:title> <dev:code>Set-PlaceV3 -Identity f12172b6-195d-4e6e-8f4f-eb72e41de99a -CountryOrRegion US -State WA -City Redmond -Street 'Street 3' -PostalCode 98052</dev:code> <dev:remarks> <maml:para>This example updates a building's address.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 3 --------------------------</maml:title> <dev:code>Set-PlaceV3 -Identity f12172b6-195d-4e6e-8f4f-eb72e41de99a -GeoCoordinates "47.644125;-122.122411"</dev:code> <dev:remarks> <maml:para>This example updates a building's geocoordinates.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 4 --------------------------</maml:title> <dev:code>Set-PlaceV3 -Identity f12172b6-195d-4e6e-8f4f-eb72e41de99a -ResourceLinks @{name="TestLink";value="https://contoso.com/";type="Url"}</dev:code> <dev:remarks> <maml:para>This example updates the resource links for a building with resource links. The entire set is replaced on update. To add or remove a value, be sure to include previous values that should be persisted.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>-------------------------- Example 5 --------------------------</maml:title> <dev:code> $mbx = New-Mailbox -Room 'DeskMailboxName' Set-Mailbox $mbx.Identity -Type Desk -HiddenFromAddressListsEnabled $true Set-PlaceV3 {DeskId} -Mailbox $mbx.ExternalDirectoryObjectId </dev:code> <dev:remarks> <maml:para>This examples creates a desk mailbox and assigns it to an existing desk entity. Please note that you need to have installed `ExchangeOnlineManagement` module and ran the `Connect-ExchangeOnline` cmdlet before running the following:</maml:para> </dev:remarks> </command:example> </command:examples> <command:relatedLinks> <maml:navigationLink> <maml:linkText>Online Version:</maml:linkText> <maml:uri>https://learn.microsoft.com/en-us/microsoft-365/places/powershell/set-placev3</maml:uri> </maml:navigationLink> </command:relatedLinks> </command:command> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp"> <command:details> <command:name>Remove-Place</command:name> <command:verb>Remove</command:verb> <command:noun>Place</command:noun> <maml:description> <maml:para>Use the Remove-Place cmdlet to delete buildings, floors, sections, desks from your Places directory.</maml:para> <maml:para>Rooms and workspaces can be removed using Exchange Remove-Mailbox.</maml:para> </maml:description> </command:details> <maml:description> <maml:para>You need to be assigned permissions before you can run this cmdlet. You must have either the Exchange Admin role or the Places TenantPlacesManagement role.</maml:para> <maml:para>You can't remove a place that is a parent of other places. Before removing a place, clear the parentId value of its existing child places before attempting to remove. As an example, clear the ParentId value on all rooms associated with a given floor before deleting that floor.</maml:para> </maml:description> <command:syntax> <command:syntaxItem> <maml:name>Remove-Place</maml:name> </command:syntaxItem> </command:syntax> <command:parameters> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="true" position="0" aliases="none"> <maml:name>Identity</maml:name> <maml:description> <maml:para>- Name_PlaceId</maml:para> <maml:para>- PlaceId</maml:para> <maml:para>Note: You can't remove a place that is a parent of other places. Before removing a place, clear the parentId value of its existing child places before attempting to remove. As an example, clear the ParentId value on all rooms associated with a given floor before deleting that floor.</maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">String</command:parameterValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <maml:alertSet> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <command:examples> <command:example> <maml:title>-------------------------- Example 1 --------------------------</maml:title> <dev:code>Remove-Place -Identity 86897e93-bcef-4c05-af9d-45116dda791f</dev:code> <dev:remarks> <maml:para>Delete a floor based on its PlaceId.</maml:para> </dev:remarks> </command:example> </command:examples> <command:relatedLinks> <maml:navigationLink> <maml:linkText>Online Version:</maml:linkText> <maml:uri>https://learn.microsoft.com/en-us/microsoft-365/places/powershell/remove-place</maml:uri> </maml:navigationLink> </command:relatedLinks> </command:command> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp"> <command:details> <command:name>Initialize-Places</command:name> <command:verb>Initialize</command:verb> <command:noun>Places</command:noun> <maml:description> <maml:para>Use the Initialize-Places cmdlet to easily create your buildings and floors, and associate rooms to those floors/buildings. The Initialize-Places cmdlet is a simplified, quick-create experience that can be used instead of creating a script using the New-Place and Set-PlaceV3 cmdlets.</maml:para> <maml:para>Setting up buildings, floors, and room associations are required to use many Places experiences, such as Places Finder.</maml:para> <maml:para>When running Initialize-Places, you can choose from 3 options:</maml:para> <maml:para>1. Export a CSV file of your conference rooms and workspaces, with additional columns for an inferred building name and floor name.</maml:para> <maml:para>2. Import a CSV file that results in automatic creation of buildings, floors, and room associations to floors/buildings.</maml:para> <maml:para>3. Import a CSV file that generates a PowerShell script that you can review and then execute to achieve the same resulting directory hierarchy as Option 2. This option is provided for tenants who would like more control or auditing of the cmdlets executed during Option 2.</maml:para> <maml:para>Please reference Quick setup of buildings and floors (https://learn.microsoft.com/en-us/microsoft-365/places/get-started/quick-setup-buildings-floors) for a tutorial guide of how to use Initialize-Places.</maml:para> </maml:description> </command:details> <maml:description> <maml:para>You need to be assigned permissions before you can run this cmdlet. You must have both the Exchange Admin role and the Places TenantPlacesManagement role. The Places role is required for the creation of buildings/floors and the MailRecipients role is required for updating the room/workspace metadata to link to the given floor/building.</maml:para> </maml:description> <command:syntax> <command:syntaxItem> <maml:name>Initialize-Places</maml:name> </command:syntaxItem> </command:syntax> <command:parameters> <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="false" position="0" aliases="none"> <maml:name>Option</maml:name> <maml:description> <maml:para>- Option 1</maml:para> <maml:para>Export your list of conference rooms and workspaces. The exported filename is ResourceAccountsMapped.csv. Initialize-Places, Option 1 only exports rooms, or workspaces associated with a room list. See the Quick setup for building and floors for an alternative of how to export all rooms and workspaces.</maml:para> <maml:para>Note: This isn't a required step if you have alternative ways that might be useful to quickly create a list of rooms/workspaces.</maml:para> <maml:para> Initialize-Places Please choose the desired option before continuing: 1. Export suggested mapping CSV of rooms to buildings/floors. 2. Import mapping CSV to automatically create buildings/floors and room mappings. 3. Export PowerShell script with commands to manually create buildings/floors and room mappings based on an imported CSV. X to cancel. 1 </maml:para> <maml:para>- Option 2</maml:para> <maml:para>Import your list of buildings and floors you want to create, and the rooms that belong to those floors/buildings. </maml:para> <maml:para>On the completion of import, the changes will be forced to reflect at Places experiences immediately and the tenant setting for "EnableBuildings" will be set to True. This will make building information visible in Places experiences, such as Outlook working hours and location, for all users of your tenant. If you prefer to keep this information hidden for now, you can use the Set-PlacesSettings cmdlet to set the setting back to False.</maml:para> <maml:para>Finally, a file will be saved into the same folder as your import file, such as _fileToImport-ImportResults.csv_, which will document whether any issues were encountered during import. </maml:para> <maml:para>The import file must be only the following 3 columns: InferredBuildingName, InferredFloorName, and PrimarySmtpAddress (of the room or workspace).</maml:para> <maml:para> Initialize-Places Please choose the desired option before continuing: 1. Export suggested mapping CSV of rooms to buildings/floors. 2. Import mapping CSV to automatically create buildings/floors and room mappings. 3. Export PowerShell script with commands to manually create buildings/floors and room mappings based on an imported CSV. </maml:para> <maml:para>- Option 3</maml:para> <maml:para>Generate a PowerShell script that can be used to create your list of buildings and floors, and setting the correct metadata on rooms and workspaces to associate them with the given floor and building. A new file is saved into the same folder as your import file, such as fileToImport-ImportResults.csv that describes any errors encountering when generating the PowerShell script. The PowerShell script will also be saved into the same folder, with the filename PlacesOnboardingScript.ps1.</maml:para> <maml:para>Despite the usage of "import" in the cmdlet wording, nothing is created into your Places Directory when using this option.</maml:para> <maml:para> Initialize-Places Please choose the desired option before continuing: 1. Export suggested mapping CSV of rooms to buildings/floors. 2. Import mapping CSV to automatically create buildings/floors and room mappings. 3. Export PowerShell script with commands to manually create buildings/floors and room mappings based on an imported CSV. </maml:para> </maml:description> <command:parameterValue required="false" variableLength="false">System.Int32</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>None</dev:defaultValue> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <maml:alertSet> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <command:relatedLinks> <maml:navigationLink> <maml:linkText>Online Version:</maml:linkText> <maml:uri>https://learn.microsoft.com/en-us/microsoft-365/places/powershell/initialize-places</maml:uri> </maml:navigationLink> </command:relatedLinks> </command:command> </helpItems> |