Microsoft Docs - Latest Articles

As the new home for Microsoft technical documentation, docs.microsoft.com has not only modernized the web experience for content, but also how we create and support the content you use to learn, manage and deploy solutions. It is the one-stop shop for everything related to Microsoft technologies. In order to make sure you can keep up to date on what’s new and exciting on docs.microsoft.com, we’ve created a dedicated feed for you.


Selected Feed: PowerShell

Windows Subsystem for Linux Command Reference

https://docs.microsoft.com/en-us/windows/wsl/reference See a list of commands that manage the Windows Subsystem for Linux, such as arguments for running Linux commands.
Published Date : Monday, July 31, 2017

Install Windows Subsystem for Linux (WSL) on Windows 10

https://docs.microsoft.com/en-us/windows/wsl/install-win10 Learn how to install the Windows Subsystem for Linux on Windows 10. Windows 10 must be updated to version 2004, build 19041 or higher.
Published Date : Tuesday, May 12, 2020

Manually download Windows Subsystem for Linux (WSL) Distros

https://docs.microsoft.com/en-us/windows/wsl/install-manual Instructions for how to manually download Windows Subsystem for Linux distributions.
Published Date : Thursday, May 28, 2020

Get started using MySQL MongoDB, PostgreSQL, SQLite, Microsoft SQL Server, or Redis to set up a database on Windows Subsystem for Linux

https://docs.microsoft.com/en-us/windows/wsl/tutorials/wsl-database Learn how to set up MySQL MongoDB, PostgreSQL, SQLite, Microsoft SQL Server, or Redis on the Windows Subsystem for Linux.
Published Date : Tuesday, July 7, 2020

Frequently Asked Questions (FAQ)

https://docs.microsoft.com/en-us/windows/wsl/faq Find answers to frequently asked questions (FAQs) about the Windows Subsystem for Linux, such as 'What can I do with WSL?'.
Published Date : Tuesday, September 4, 2018

Comparing WSL 2 and WSL 1

https://docs.microsoft.com/en-us/windows/wsl/compare-versions Compare version 1 and version 2 of the Windows Subsystem for Linux. WSL 2 runs an actual Linux kernel, increasing speed and full system call compatibility. WSL 1 works better if your working across BOTH Windows and Linux file systems.
Published Date : Wednesday, July 22, 2020

Azure NetAppFiles SDK SMB Sample .NETCore - Code Samples

https://docs.microsoft.com/en-us/samples/azure-samples/netappfiles-dotnetcore-smb-sdk-sample/azure-netappfiles-sdk-smb-sample-netcore/ This project demonstrates how to use dotnet-core with NetApp Files SDK for Microsoft.NetApp resource provider to deploy a SMB Volume.
Published Date : Monday, August 31, 2020

Get-Whiteboard (MicrosoftWhiteboardAdmin)

https://docs.microsoft.com/en-us/powershell/module/whiteboard/get-whiteboard Gets one or more Whiteboards from the Microsoft Whiteboard service and returns them as objects.
Published Date : Monday, April 23, 2018

Invoke-TransferAllWhiteboards (MicrosoftWhiteboardAdmin)

https://docs.microsoft.com/en-us/powershell/module/whiteboard/invoke-transferallwhiteboards Transfer ownership of all Whiteboards owned by a user to another user.
Published Date : Monday, April 23, 2018

Microsoft Whiteboard PowerShell

https://docs.microsoft.com/en-us/powershell/whiteboard/ Welcome to the Microsoft Whiteboard PowerShell cmdlet help references. ... Here you will find all of the Microsoft Whiteboard PowerShell help topics. ... The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.
Published Date : Monday, April 23, 2018

Add-SPMTTask (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/add-spmttask Add a new migration task to the registered migration session. Currently there are three different types of tasks allowed: File Share task, SharePoint task and JSON defined task.
Published Date : Wednesday, September 16, 2020

Get-SPMTMigration (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/get-spmtmigration Return object of current session. It includes current tasks status and current session level settings.
Published Date : Wednesday, September 16, 2020

Stop-SPMTMigration (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/stop-spmtmigration Cancel the current migration session.
Published Date : Wednesday, September 16, 2020

Remove-SPMTTask (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/remove-spmttask Remove an existing migration task from the registered migration.
Published Date : Wednesday, September 16, 2020

Unregister-SPMTMigration (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/unregister-spmtmigration Remove the SPMT migration session created.
Published Date : Wednesday, September 16, 2020

Register-SPMTMigration (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/register-spmtmigration This cmdlet will create a migration session and initialize it. The initialization will configure migration settings at session level. If no specific setting parameters are defined, default settings will be used. After a session is registered, the user can add a migration task to the migration session and start migration.
Published Date : Wednesday, September 16, 2020

Show-SPMTMigration (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/show-spmtmigration If the user starts the migration with -NoShow parameter, running the ‘Show-SPMTMigration’ cmdlet will display the task ID, data source location, target location and migration status in the console. Pressing Ctrl+C will return to NoShow mode.
Published Date : Wednesday, September 16, 2020

Start-SPMTMigration (SharePointMigrationTool)

https://docs.microsoft.com/en-us/powershell/module/spmt/start-spmtmigration This cmdlet will start the registered SPMT migration.
Published Date : Wednesday, September 16, 2020

Connect-MicrosoftTeams (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/connect-microsoftteams The Connect-MicrosoftTeams cmdlet connects an authenticated account to use for Microsoft Teams cmdlet requests. You can use this authenticated account only with Microsoft Teams cmdlets.
Published Date : Wednesday, September 16, 2020

Get-TeamMessagingSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teammessagingsettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To retrieve a Team's messaging settings, run Get-Team. Gets team messaging settings.
Published Date : Wednesday, September 16, 2020

Get-CsUserPolicyAssignment (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-csuserpolicyassignment This cmdlets returns the effective policies for a user, based on either direct policy assignment or inheritance from a group policy assignment. For a given policy type, if an effective policy is not returned, this indicates that the effective policy for the user is either the tenant global default policy (if set) or the system global default policy. This cmdlet does not currently support returning policies for multiple users.
Published Date : Wednesday, September 16, 2020

New-Team (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/new-team Creates a new team with user specified settings, and returns a Group object with a GroupID property. Note that Templates are not yet supported in our 1.0 PowerShell release.
Published Date : Wednesday, September 16, 2020

Get-TeamChannelUser (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamchanneluser Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Get-TeamUser (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamuser Returns an array containing the UPN, UserId, Name and Role of users belonging to an specific GroupId.
Published Date : Wednesday, September 16, 2020

Get-TeamsAppInstallation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamsappinstallation Get a Teams App installed in Microsoft Teams. Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Get-TeamMemberSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teammembersettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To retrieve a Team's member settings, run Get-Team. Gets team member settings.
Published Date : Wednesday, September 16, 2020

Set-Team (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-team This cmdlet allows you to update properties of a team, including its displayname, description, and team-specific settings. This cmdlet includes all settings that used to be set using the Set-TeamFunSettings, Set-TeamGuestSettings, etc. cmdlets
Published Date : Wednesday, September 16, 2020

Add-TeamUser (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/add-teamuser This cmdlet adds an owner or member to the team, and to the unified group which backs the team. Note The command will return immediately, but the Teams application will not reflect the update immediately. The change can take between 24 and 48 hours to appear within the Teams client.
Published Date : Wednesday, September 16, 2020

New-CsGroupPolicyAssignment (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/new-csgrouppolicyassignment This is used to assign a policy to a security group or distribution list. The policy assignment will then be propagated to the members of the group (even if members are added to the group later) in accordance with the rules for group policy inheritance. If a user is directly assigned a policy of a specific type, then they will not inherit a policy of the same type from a group. If a user is a member of two or more groups that each have a policy of the same type assigned, then the user will inherit the policy based on the group policy assignment with the highest rank. The group policy assignment rank is set at the time a policy is being assigned to a group and is relative to other group policy assignments of the same policy type. For example, if there are two groups, each assigned a Teams Meeting policy, then one of the group assignments will be rank 1 while the other will be rank 2. It's helpful to think of rank as determining the position of each policy assignment in an ordered list, from highest rank to lowest rank. In fact, rank can be specified as any number, but these are converted into sequential values 1, 2, 3, etc. with 1 being the highest rank. When assigning a policy to a group, set the rank to be the position in the list where you want the new group policy assignment to be. If a rank is not specified, the policy assignment will be given the lowest rank, corresponding to the end of the list. Group policy assignment allows you to easily manage policies across different subsets of users within your organization. Group policy assignment is recommended for groups of up to 50000 users, but it will also work with larger groups. Group policy assignments are only propagated to users that are direct members of the group; the assignments are not propagated to members of nested groups. Group policy assignment is currently limited to the following policy types: CallingLineIdentity (Caller ID policies), OnlineVoiceRoutingPolicy (Voice Routing policies), TeamsAppSetupPolicy (App Setup policies), TeamsCallingPolicy (Calling policies), TeamsCallParkPolicy (Call park policies), TeamsChannelsPolicy, TeamsComplianceRecordingPolicy, TenantDialPlan, TeamsEducationAssignmentsAppPolicy, TeamsMeetingBroadcastPolicy (Live Events policies), TeamsMeetingPolicy (Meeting policies), TeamsMessagingPolicy (Messaging policies), TeamsUpdateManagementPolicy.
Published Date : Wednesday, September 16, 2020

Get-CsBatchPolicyAssignmentOperation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-csbatchpolicyassignmentoperation This cmdlets returns the status of all batch policy assignment operations for the last 30 days. If an operation ID is specified, the detailed status for that operation is returned including the status for each user in the batch.
Published Date : Wednesday, September 16, 2020

Get-CsGroupPolicyAssignment (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-csgrouppolicyassignment This cmdlets returns group policy assignments. Optional parameters allow the results to be restricted to policies assigned to a specific group or policies of a specific type.
Published Date : Wednesday, September 16, 2020

Remove-TeamsApp (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamsapp Removes an app in the Teams tenant app store.
Published Date : Wednesday, September 16, 2020

Get-CsPolicyPackage (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-cspolicypackage This cmdlet supports retrieving all the policy packages available on a tenant. Provide the identity of a specific policy package to retrieve its definition, including details on the policies applied with the package. For more information on policy packages, please review https://docs.microsoft.com/MicrosoftTeams/manage-policy-packages.
Published Date : Wednesday, September 16, 2020

New-TeamChannel (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/new-teamchannel Important Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here https://www.poshtestgallery.com/packages/MicrosoftTeams.
Published Date : Wednesday, September 16, 2020

Remove-TeamChannelUser (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamchanneluser Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Update-TeamsAppInstallation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/update-teamsappinstallation Update a Teams App in Microsoft Teams. Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Remove-TeamsAppInstallation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamsappinstallation Removes a Teams App installed in Microsoft Teams. Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Get-TeamGuestSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamguestsettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To retrieve a Team's guest settings, run Get-Team. Gets Team guest settings.
Published Date : Wednesday, September 16, 2020

Set-TeamMemberSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teammembersettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To set a Team's settings, run Set-Team. Updates team member settings.
Published Date : Wednesday, September 16, 2020

Set-CsGroupPolicyAssignment (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-csgrouppolicyassignment This cmdlet will update the policy assignment for a group for a given policy type. The policy instance and/or policy rank can be updated. Refer to New-CsGroupPolicyAssignment for more details about rank.
Published Date : Wednesday, September 16, 2020

Set-TeamChannel (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teamchannel Important Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here https://www.poshtestgallery.com/packages/MicrosoftTeams.
Published Date : Wednesday, September 16, 2020

New-TeamsApp (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/new-teamsapp Use a Teams app manifest zip file to upload an app to the tenant app store. DistributionMethod specifies that the app should be added to the organization.
Published Date : Wednesday, September 16, 2020

Set-TeamGuestSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teamguestsettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To set a Team's settings, run Set-Team. Updates team guest settings.
Published Date : Wednesday, September 16, 2020

Get-Team (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-team This cmdlet supports retrieving teams with particular properties/information, including all teams that a specific user belongs to, all teams that have been archived, all teams with a specific display name, or all teams in the organization. Note Depending on the number of teams and O365 Groups in your organization and which filters you are using, this cmdlet can take upwards of ten minutes to run. Some of the input parameters are guaranteed unique (e.g. GroupId), and others serve as filters (e.g. -Archived).
Published Date : Wednesday, September 16, 2020

Add-TeamChannelUser (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/add-teamchanneluser Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Remove-Team (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-team Removes a specified team via GroupID and all its associated components, like O365 Unified Group...
Published Date : Wednesday, September 16, 2020

Grant-CsUserPolicyPackage (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/grant-csuserpolicypackage This cmdlet supports applying a policy package to users in a tenant. Provide one or more user identities to assign the package with all the associated policies. The available policy packages and their definitions can be found by running Get-CsPolicyPackage. The recommended policy package for each user can be found by running Get-CsUserPolicyPackageRecommendation. For more information on policy packages, please review https://docs.microsoft.com/MicrosoftTeams/manage-policy-packages.
Published Date : Wednesday, September 16, 2020

Get-TeamsApp (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamsapp Use any optional parameter to retrieve app information from the Teams tenant app store.
Published Date : Wednesday, September 16, 2020

Set-TeamArchivedState (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teamarchivedstate This cmdlet is used to freeze all of the team activity and also specify whether SharePoint site should be marked as Read-Only. Teams administrators and team owners will still be able to add or remove members and update roles. You can unarchive the team anytime.
Published Date : Wednesday, September 16, 2020

Get-CsUserPolicyPackage (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-csuserpolicypackage This cmdlet supports retrieving the policy package that's assigned to a user. Provide the identity of a user to retrieve the definition of their assigned policy package. For more information on policy packages, please review https://docs.microsoft.com/MicrosoftTeams/manage-policy-packages.
Published Date : Wednesday, September 16, 2020

MicrosoftTeamsPowerShell Module

https://docs.microsoft.com/en-us/powershell/module/teams/ The following cmdlet references are for Microsoft Teams.
Published Date : Wednesday, September 16, 2020

Remove-TeamUser (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamuser Remove an owner or member from a team, and from the unified group which backs the team. Note: the command will return immediately, but the Teams application will not reflect the update immediately. The Teams application may need to be open for up to an hour before changes are reflected. Note: last owner cannot be removed from the team.
Published Date : Wednesday, September 16, 2020

New-CsBatchPolicyAssignmentOperation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/new-csbatchpolicyassignmentoperation When a policy is assigned to a batch of users, the assignments are performed as an asynchronous operation. The cmdlet returns the operation ID which can be used to track the progress and status of the assignments. Users can be specified by their object ID (guid) or by their SIP address (user. Note that a user's SIP address often has the same value as the User Principal Name (UPN), but this is not required. If a user is specified using their UPN, but it has a different value than their SIP address, then then policy assignment will fail for the user. A batch may contain up to 5,000 users. If a batch includes duplicate users, the duplicates will be removed from the batch before processing and status will only be provided for the unique users remaining in the batch. For best results, do not submit more than a few batches at a time. Allow batches to complete processing before submitting more batches. You must be a Teams service admin, a Teams communication admin, or Global Administrator to run the cmdlet. Batch policy assignment is currently limited to the following policy types: CallingLineIdentity, ExternalAccessPolicy, OnlineVoiceRoutingPolicy, TeamsAppSetupPolicy, TeamsAppPermissionPolicy, TeamsCallingPolicy, TeamsCallParkPolicy, TeamsChannelsPolicy, TeamsEducationAssignmentsAppPolicy, TeamsEmergencyCallingPolicy, TeamsMeetingBroadcastPolicy, TeamsEmergencyCallRoutingPolicy, TeamsMeetingPolicy, TeamsMessagingPolicy, TeamsUpdateManagementPolicy, TeamsUpgradePolicy, TeamsVerticalPackagePolicy, TeamsVideoInteropServicePolicy, TenantDialPlan
Published Date : Wednesday, September 16, 2020

Get-TeamChannel (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamchannel Get all the channels for a team.
Published Date : Wednesday, September 16, 2020

Set-TeamPicture (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teampicture Important Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here https://www.poshtestgallery.com/packages/MicrosoftTeams.
Published Date : Wednesday, September 16, 2020

Set-TeamFunSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teamfunsettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To set a Team's settings, run Set-Team. Update Giphy, Stickers and Memes settings.
Published Date : Wednesday, September 16, 2020

Remove-TeamChannel (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamchannel Important Modules in the PS INT gallery for Microsoft Teams run on the /beta version in Microsoft Graph and are subject to change. Int modules can be install from here https://www.poshtestgallery.com/packages/MicrosoftTeams.
Published Date : Wednesday, September 16, 2020

Add-TeamsAppInstallation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/add-teamsappinstallation Add a Teams App to Microsoft Teams. Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes.
Published Date : Wednesday, September 16, 2020

Get-CsUserPolicyPackageRecommendation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-csuserpolicypackagerecommendation This cmdlet supports retrieving recommendations for which policy packages are best suited for a given user. This recommendation is based on tenant and user information such as license types. For more information on policy packages, please review https://docs.microsoft.com/MicrosoftTeams/manage-policy-packages.
Published Date : Wednesday, September 16, 2020

Get-TeamFunSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/get-teamfunsettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To retrieve a Team's fun settings, run Get-Team. Gets a team's fun settings.
Published Date : Wednesday, September 16, 2020

Set-TeamMessagingSettings (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teammessagingsettings Note: This cmdlet is deprecated as of our 1.0 PowerShell release, and is not supported in our 1.0 release. To set a Team's settings, run Set-Team. Updates team messaging settings.
Published Date : Wednesday, September 16, 2020

New-CsBatchPolicyPackageAssignmentOperation (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/new-csbatchpolicypackageassignmentoperation This cmdlet submits an operation that applies a policy package to a batch of users in a tenant. Provide one or more user identities to assign the package with all the associated policies. The available policy packages and their definitions can be found by running Get-CsPolicyPackage. The recommended policy package for each user can be found by running Get-CsUserPolicyPackageRecommendation. For more information on policy packages, please review https://docs.microsoft.com/MicrosoftTeams/manage-policy-packages.
Published Date : Wednesday, September 16, 2020

Set-TeamsApp (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/set-teamsapp Use a Teams app manifest zip file to upload an app to the tenant app store.
Published Date : Wednesday, September 16, 2020

Remove-CsGroupPolicyAssignment (MicrosoftTeamsPowerShell)

https://docs.microsoft.com/en-us/powershell/module/teams/remove-csgrouppolicyassignment This cmdlet removes the policy of a specific type from a group. A group can only be assigned one policy of a given type, so the name of the policy to be removed does not need to be specified. When a policy assignment is removed from a group, any other group policy assignments of the same type that have lower rank will be updated. For example, if the policy assignment with rank 2 is removed, then the rank 3 and 4 policy assignments will be updated to rank 2 and 3 respectively.
Published Date : Wednesday, September 16, 2020

Import-StaffHubMember (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/import-staffhubmember Import a list of members and add them to teams. Format of the file context - TeamId,FirstName,LastName,Email,PhoneNumber,IsManager. Either Email or PhoneNumber is required. Eg: TEAM_1234,Staff,five,abc Failure in adding one member does not stop the other members from getting added.
Published Date : Monday, September 25, 2017

Get-StaffHubUsersForTenant (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/get-staffhubusersfortenant Get all the StaffHub users in the tenant of the logged in user. ContinuationToken from the call is stored in $nextToken variable. Here is an example of the next call that can be made: Get-StaffHubUsersForTenant -Top 10 -ContinuationToken $nextToken
Published Date : Monday, September 25, 2017

Import-StaffHubTeam (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/import-staffhubteam Imports a set of teams from a specified file. Format of the File content - Name,TimeZone,ManagerEmail Eg: CmdletTestTeam,Asia/Calcutta,abc Failure in adding one team does not stop the other teams from getting added.
Published Date : Monday, September 25, 2017

Get-StaffHubTeamsForTenant (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/get-staffhubteamsfortenant Get all the teams in the tenant of the logged in user. ContinuationToken from the call is stored in $nextToken Variable. So the next call can be made like Get-StaffHubTeamsForTenant -Top 10 -ContinuationToken $nextToken.
Published Date : Monday, September 25, 2017

Add-StaffHubMember (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/add-staffhubmember Adds a member or manager to the specified team.
Published Date : Monday, September 25, 2017

Connect-StaffHub (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/connect-staffhub The Connect-StaffHub cmdlet connects an authenticated account. This cmdlet authenticates a user for Staff Hub. You can use this authenticated account only with Microsoft StaffHub cmdlets.
Published Date : Monday, September 25, 2017

Add-StaffHubShift (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/add-staffhubshift Adds a shift to the specified member in a team.
Published Date : Monday, September 25, 2017

Import-StaffHubShift (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/import-staffhubshift Imports a list of shifts and adds them to members in the specified teams. Format of the file content - Title,Notes,StartDateTime,EndDateTime,ShiftType,MemberId,TeamId Eg: Title,Notes,2018-11-28T00:00:00Z,2018-11-28T02:00:00Z,Working,MBER_1234,TEAM_1234 Failure in adding one shift does not stop the other shifts from getting added.
Published Date : Monday, September 25, 2017

Get-StaffHubShifts (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/get-staffhubshifts Get details of the shifts for all team members or for a specified team member
Published Date : Monday, September 25, 2017

Remove-StaffHubUser (MicrosoftStaffHubPowerShell)

https://docs.microsoft.com/en-us/powershell/module/staffhub/remove-staffhubuser Removes the specified user from StaffHub. Pre-requisite is to delete the user from AAD.
Published Date : Monday, September 25, 2017

Update-CsClsLogging (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csclslogging The centralized logging service (which replaces the OCSLogger and OCSTracer tools used in Microsoft Lync Server 2010) provides a way for administrators to manage logging and tracing for all computers and pools running Skype for Business Server. Centralized logging enables administrators to stop, start, and configure logging for one or more pools and computers by using a single command; for example, you can use one command to enable Address Book service logging on all your Address Book servers. This differs from the OCSLogger and OCSTracer tools, which had to be individually managed (including individually stopped and started) on each server. In addition, the centralized logging service also provides a way for administrators to search trace logs from the command, using the Windows PowerShell command-line interface and the Search-CsClsLogging cmdlet. Centralized logging is built around a series of predefined scenarios that offer a more finely-targeted approach to logging than offered in previous versions of Skype for Business Server. These scenarios predetermine the server components and logging for you; as a result, an administrator enabling the RGS scenario can be confident that he or she will only log information relevant to the Response Group service and not to, say, the audio conferencing provider service. It is also possible to define custom scenarios by using the New-CsClsScenario cmdlet. By default, logging operations run for 4 hours (240 minutes) before automatically stopping; however, administrators have the option of specifying a different duration time when they begin logging. In addition, administrators can also use the Update-CsClsLogging cmdlet to change the duration time for all the scenarios currently being logged.
Published Date : Monday, September 25, 2017

Update-CsUserData (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csuserdata The Update-CsUserData cmdlet enables administrators to update user data for a specified user or set of users. (Note that this data must have previously been exported by using the Export-CsUserData cmdlet.) This updating is typically done in order to restore lost data to a logged-on user. Skype for Business Server Control Panel: The functions carried out by the Update-CsUserData cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Update-CsUserDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csuserdatabase The Skype for Business Server user database holds detailed information about such things as contacts, groups, and access permissions. As such, the database is required to periodically synchronize its contents with the information stored in Active Directory. More often than not, the automatic synch between the user database and Active Directory will keep the information in the user database up to date. However, it is possible that a problem might occur that prevents this automatic synchronization from taking place. In a case such as that, you can use the Update-CsUserDatabase cmdlet to force the user database to refresh its contents by re-reading all of the user information stored in Active Directory. You might also need to run this cmdlet if a product update ever includes a change to the user replicator service.
Published Date : Monday, September 25, 2017

Test-CsWebApp (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-cswebapp The Test-CsWebApp cmdlet enables administrators to verify that authenticated users can employ Skype for Business Web App in order to join conferences. When you run the Test-CsWebApp cmdlet, the cmdlet attempts to obtain web tickets for a pair of test users by using the Web Ticket service. If the tickets can be obtained, and the test users authenticated, the Test-CsWebApp cmdlet will then try to connect to Skype for Business Server by using Skype for Business Web App. If the connection is made, the cmdlet will then attempt to establish separate conferences for instant messaging, application sharing, and data collaboration. Many administrators will use the CsHealthMonitoringConfiguration cmdlets to set up test users for each of their Registrar pools. These test users represent a pair of user accounts that have been preconfigured for use with synthetic transactions. (Typically these are test accounts and not accounts that belong to actual users.) If test users are configured for a pool, administrators can run the Test-CsWebApp cmdlet against that pool without having to specify the identity of (and supply the credentials for) the user account involved in the test. Alternatively, administrators can run the Test-CsWebApp cmdlet using actual user accounts. If you decide to conduct the test using actual user accounts you will need to supply the logon name and password for each account.
Published Date : Monday, September 25, 2017

Update-CsOrganizationalAutoAttendant (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csorganizationalautoattendant This cmdlet provides a way to update the resources associated with an auto attendant configured for use in your organization. Currently, it repairs the Dial-by-Name recognition status and the SIP provisioning status of an auto attendant. Note: This cmdlet only triggers the refresh of auto attendant resources. It does not wait until all the resources have been refreshed. The last completed status of auto attendant can be retrieved using Get-CsOrganizationalAutoAttendantStatus cmdlet.
Published Date : Monday, September 25, 2017

Test-CsWebAppAnonymous (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-cswebappanonymous The Test-CsWebAppAnonymous cmdlet enables administrators to verify that anonymous users can employ Skype for Business Web App in order to join conferences. When you run the Test-CsWebAppAnonymous cmdlet, the cmdlet attempts to obtain an anonymous web ticket by using the Web Ticket service. If the ticket can be obtained, the Test-CsWebAppAnonymous cmdlet will then try to connect to by Skype for Business Server using Skype for Business Web App. If the connection is made, the cmdlet will then attempt to establish separate conferences for instant messaging, application sharing, and data collaboration. Many administrators will use the CsHealthMonitoringConfiguration cmdlets to set up test users for each of their Registrar pools. These test users represent a pair of user accounts that have been preconfigured for use with synthetic transactions. (Typically these are test accounts and not accounts that belong to actual users.) If test users are configured for a pool, administrators can run the Test-CsWebAppAnonymous cmdlet against that pool without having to specify the identity of (and supply the credentials for) the user account involved in the test. Alternatively, administrators can run the Test-CsWebAppAnonymous cmdlet using an actual user account. If you decide to conduct the test using an actual user account you will need to supply the logon name and password for that account.
Published Date : Monday, September 25, 2017

Update-CsAddressBook (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csaddressbook Address Book servers are intermediaries between Active Directory and Skype for Business Server. The Address Book server ensures that the user information stored in Skype for Business Server is in synch with the user information stored in Active Directory. This is done by periodically synching Address Book files with the information stored in the User database. By default, this synchronization takes place every five minutes. (However, that time interval can be modified by using the Set-CsAddressBookConfiguration cmdlet.) If you can't wait for synchronization to take place or if it appears that, for some reason, synchronization isn't taking place, you can use the Update-CsAddressBook cmdlet to force an Address Book server to immediately synch with the user information stored in the User database.
Published Date : Monday, September 25, 2017

Update-CsAdminRole (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csadminrole The Update-CsAdminRole cmdlet provides a way for you to update the RBAC role definitions stored in the Central Management database. This cmdlet is typically used in coexistence/migration. Skype for Business Server Control Panel: The functions carried out by the Update-CsAdminRole cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Test-CsVoiceTestConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-csvoicetestconfiguration Before implementing voice routes and voice policies, it's a good idea to test them out on various phone numbers to ensure the results are what you're expecting. Running this cmdlet with the appropriate parameter settings allows you to run these tests. This cmdlet tests a phone number against a voice route, usage, dial plan, and voice policy to enable you to verify intended outcomes or to compare the actual outcome to the expected outcome. The voice configurations to be tested can be defined by entering the appropriate parameters individually, or by using the New-CsVoiceTestConfiguration cmdlet. If you enter values for DialedNumber, DialPlan, and VoicePolicy, the output will include the translated number, the normalization rule used to create that translation, the route that was used, and the PSTN usage. If instead you enter a value for the TestCaseInputObject parameter, you can also retrieve status on whether the results matched expected results that you supplied to the test object when you created it with the New-CsVoiceTestConfiguration cmdlet.
Published Date : Monday, September 25, 2017

Uninstall-CsMirrorDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/uninstall-csmirrordatabase Mirror databases enable you to simultaneously maintain two copies of a database: when data is written to Database A, a copy of that data is also written to its mirror database. This provides the ability to instantly replace Database A should that database become unavailable: you can "failover" to the mirror database with minimal disruption to your users and with minimal data loss. Mirror databases can be installed and configured by using the Install-CsMirrorDatabase cmdlet. If you ever need to remove a mirror database, you can do so by using the Uninstall-CsMirrorDatabase cmdlet. Skype for Business Server Control Panel: The functions carried out by the Uninstall-CsMirrorDatabase cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Uninstall-CsDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/uninstall-csdatabase Skype for Business Server makes extensive use of SQL Server databases such as the Central Management store and the Archiving database. These databases are set up at the same time you install Skype for Business Server or at the same time you install a Skype for Business Server role that requires a database back end. After the databases have been installed, you will rarely need to uninstall them. However, it is possible that you might need to uninstall a Skype for Business Server database at some point; for example, a hardware failure or an issue with network connectivity might make an existing database unusable. Regardless of the reason, the Uninstall-CsDatabase cmdlet provides a way for you to remove or detach any of the SQL Server databases used by Skype for Business Server.
Published Date : Monday, September 25, 2017

Update-CsAutoAttendant (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-csautoattendant This cmdlet provides a way to update the resources associated with an auto attendant configured for use in your organization. Currently, it repairs the Dial-by-Name recognition status of an auto attendant. Note: This cmdlet only triggers the refresh of auto attendant resources. It does not wait until all the resources have been refreshed. The last completed status of auto attendant can be retrieved using Get-CsAutoAttendantStatus cmdlet.
Published Date : Monday, September 25, 2017

Test-CsPstnOutboundCall (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-cspstnoutboundcall The Test-CsPstnOutboundCall cmdlet is an example of a Skype for Business Server "synthetic transaction." Synthetic transactions are used in Skype for Business Server to verify that users are able to successfully complete common tasks such as logging on to the system, exchanging instant messages, or making calls to a phone located on the public switched telephone network (PSTN). These tests can be conducted manually by an administrator, or they can be automatically run by an application such as Microsoft System Center Operations Manager (formerly Microsoft Operations Manager). Synthetic transactions are typically conducted in two different ways. Many administrators will use the CsHealthMonitoringConfiguration cmdlets to set up test users for each of their Registrar pools. These test users are a pair of users who have been preconfigured for use with synthetic transactions. (Typically these are test accounts and not accounts that belong to actual users.) With test users configured for a pool, administrators can simply run a synthetic transaction against that pool without having to specify the identities of (and supply the credentials for) the user accounts involved in the test. Alternatively, administrators can run a synthetic transaction using actual user accounts. For example, if two users are unable to exchange instant messages, an administrator could run a synthetic transaction using the two user accounts in question (as opposed to a pair of test accounts) and try to diagnose and resolve the problem. If you decide to conduct a synthetic transaction using actual user accounts you will need to supply the logon names and passwords for each user. Test-CsPstnOutboundCall can also be used in server platform mode. In that case you only need to specify the SIP address of a user, and Skype for Business Server will use certificates to authenticate that user. When you run the Test-CsPstnOutboundCall cmdlet, the cmdlet first attempts to log the test user on to Skype for Business Server. If the logon succeeds, the cmdlet will then attempt to make a phone call across the PSTN gateway. This phone call will be placed using the dial plan, voice policy, and other policies and settings assigned to the test account. When the call is answered, the cmdlet sends dual-tone multi-frequency (DTMF) codes across the network in order to verify media connectivity. When conducting its test, the Test-CsPstnOutboundCall cmdlet will make an actual phone call: the target phone will ring and must be answered for the test to succeed. This call must also be manually ended by the administrator.
Published Date : Monday, September 25, 2017

Update-CsTenantMeetingUrl (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/update-cstenantmeetingurl The Update-CsTenantMeetingUrl updates the Skype for Business Online meeting URL to a simpler and more standardized format; this helps eliminate problems that occasionally occurred with the original meeting URL. For example, suppose an organization sets up an Office 365 domain with the name contoso.onmicrosoft.com. When they do that, meetings will have URLs similar to this: https://meet.lync.com/onmicrosoft/contoso/user1/45GZFH99 Now, suppose the organization undergoes some changes and decides to use the "vanity" URL litwareinc.com instead of the onmicrosoft.com URL. The organization modifies their user email addresses to use the litwareinc.com domain. However, meeting URLs will still use the old domain name: https://meet.lync.com/contoso/user1/45GZFH99 To fix this problem, administrators should run the Update-CsTenantMeetingUrl cmdlet. That will replace the old meeting URL with a new one that features the vanity URL instead: https://meet.lync.com/litwareinc.com/user1/37JYLP71 Running the Update-CsTenantMeetingUrl cmdlet is the only way to make this change. Note that, when you run Update-CsTenantMeetingUrl, your Skype for Business Online tenant will switch to the new URL immediately. That will not create any problems for new meetings that your users might schedule: those meetings will automatically be scheduled using the new URL. However, previously-scheduled meetings will run into problems; that's because they were scheduled using the older, defunct meeting URL. The only way to address this issue is to have your users reschedule those meetings. Because this could potentially create problems in some organizations (particularly organizations where a large number of meetings have already been scheduled), by default Update-CsTenantMeetingUrl will prompt you before actually updating the meeting URL: WARNING: This is a breaking change for users in this tenant. Meeting URL configuration will be updated!Old meeting URLs will no longer function. This change cannot be reverted. Are you sure you want to continue? [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): You must answer "Yes" or "Yes to All" before the command will actually be executed; if you answer "No" then the command will be cancelled and the meeting URL will not be updated. Keep in mind that once the meeting URL has been changed there is no way to revert back to the original URL. Once the command executes the URL will be changed and all previously-scheduled meetings will need to be rescheduled. This also means that you only need to run this command once per tenant. There is no need to periodically run and the command and re-update the meeting URL. If you prefer to run the command without having to address the confirmation prompt, you can include the Force parameter. In that case, Update-CsTenantMeetingUrl will run without displaying the confirmation prompt: WARNING: This is a breaking change for users in this tenant. Meeting URL configuration will be updated!
Published Date : Monday, September 25, 2017

Test-CsRegistration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-csregistration The Test-CsRegistration cmdlet is an example of a Skype for Business Server "synthetic transaction." Synthetic transactions are used in Skype for Business Server to verify that users are able to successfully complete common tasks such as logging on to the system, exchanging instant messages, or making calls to a phone located on the public switched telephone network (PSTN). These tests can be conducted manually by an administrator, or they can be automatically run by an application such as Microsoft System Center Operations Manager (formerly Microsoft Operations Manager). Synthetic transactions are typically conducted in two different ways. Many administrators will use the CsHealthMonitoringConfiguration cmdlets to set up test users for each of their Registrar pools. These test users are a pair of users who have been preconfigured for use with synthetic transactions. (Typically these are test accounts and not accounts that belong to actual users.) With test users configured for a pool, administrators can simply run a synthetic transaction against that pool without having to specify the identities of (and supply the credentials for) the user accounts involved in the test. Alternatively, administrators can run a synthetic transaction using actual user accounts. For example, if two users are unable to exchange instant messages, an administrator could run a synthetic transaction using the two user accounts in question (as opposed to a pair of test accounts) and try to diagnose and resolve the problem. If you decide to conduct a synthetic transaction using actual user accounts you will need to supply the logon names and passwords for each user. The Test-CsRegistration cmdlet enables you to verify that users in your organization can log on to Skype for Business Server. In order to perform this check, the Test-CsRegistration cmdlet requires a single test account. If you have set up test users for the pool where the test is to be conducted, then you do not need to specify an account; instead, the Test-CsRegistration cmdlet will automatically use the first test account that was assigned to the pool. (For details, see the New-CsHealthMonitoringConfiguration cmdlet help topic.) Alternatively, you can conduct the test using an account that has not been assigned to the pool. This allows you run tests even if you have not configured test users. It also allows you to test the ability of a specific user to log on to Skype for Business Server. (If you choose to use this approach, you will need to provide the user name and password for the account being tested.) When you run the Test-CsRegistration cmdlet, the cmdlet attempts to sign the test user on to Skype for Business Server and then, if successful, disconnects that test user from the system. All of this happens without any user interaction, and without affecting any actual users. For example, suppose the test account sip:kenmyer corresponds to a real user with a real Skype for Business Server account. In that case, the test will be conducted without any disruption to the real Ken Myer. When the Ken Myer test account logs off from the system, Ken Myer the person will remain logged on. Adding the Verbose parameter enables you to get a detailed account of all the actions taken by the Test-CsRegistration cmdlet in order to complete its test.
Published Date : Monday, September 25, 2017

Test-CsXmppIM (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-csxmppim The Extensible Messaging and Presence Protocol (XMPP) is a standard communications protocol (based on XML) used for sending messages across the Internet. XMPP was originally named Jabber, and is supported by a number of Internet messaging and communication applications, including Google Talk and Facebook Chat. The Test-CsXmppIM cmdlet verifies that a user can exchange instant messages with a user on an XMPP network. Note that, for this test to succeed, you must have a valid SIP address for the XMPP user, and that SIP address must be on a network that has been configured as an allowed XMPP partner. Skype for Business Server Control Panel: The functions carried out by the Test-CsXmppIM cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Test-CsTopology (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-cstopology The Test-CsTopology cmdlet provides a way for you to verify that Skype for Business Server is functioning correctly at a global level. By default, the cmdlet checks your entire Skype for Business Server infrastructure, verifying that the required services are running and that the appropriate permissions have been set for these services and for the universal security groups created when you install Skype for Business Server. In addition to verifying the validity of Skype for Business Server as a whole, the Test-CsTopology cmdlet also lets you check the validity of a specific service. For example, this command checks the state of the A/V Conferencing Server on the pool atl-cs-001.litwareinc.com: Test-CsTopology -Service "ConferencingServer:atl-cs-001.litwareinc.com"
Published Date : Monday, September 25, 2017

Unregister-CsOnlineDialInConferencingServiceNumber (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/unregister-csonlinedialinconferencingservicenumber Unassigns the previously assigned service number as default Conference Bridge number.
Published Date : Monday, September 25, 2017

Unlock-CsClientPin (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/unlock-csclientpin Skype for Business Server enables users to connect to the system or to join public switched telephone network (PSTN) conferences by using a telephone. Typically, logging on to the system or joining a conference requires the user to enter a user name or password. However, entering a user name and password can be a problem if you are using a phone that does not have an alphanumeric keypad. Because of that, Skype for Business Server enables you to supply users with numeric-only PINs; when prompted, users can then log on to the system or join a conference by entering the PIN instead of a user name and password. This is true, however, only if the user's PIN is unlocked. If a PIN has been locked (either because the user repeatedly failed to log on or because an administrator explicitly locked the PIN), the user will not be able to access the system or join a conference by using PIN authentication. (However, that user will still be able to use an application such as Skype for Business to log on to the system by supplying a user name and password.) If a PIN has been locked, there is only one way to restore the user's ability to access the system by using PIN authentication: the locked PIN must be unlocked by an administrator. This can be done by using the Unlock-CsClientPin cmdlet. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. That means that you will not be able to run the Unlock-CsClientPin cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on the Standard Edition server itself.) To run the Unlock-CsClientPin cmdlet remotely against a Standard Edition server you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Test-CsTrunkConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-cstrunkconfiguration Use this cmdlet to verify that a trunking configuration performs as expected against a dialed phone number. Each configuration contains specific settings defining the relationship and capabilities between the Mediation Server and the public switched telephone network (PSTN) gateway, IP-public branch exchange (PBX), or Session Border Controller (SBC) at the service provider. These settings configure such things as whether media bypass is enabled on this trunk, whether real-time transport control protocol (RTCP) packets are sent under certain conditions, and whether to require secure real-time protocol (SRTP) encryption.
Published Date : Monday, September 25, 2017

Test-CsVoiceRoute (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-csvoiceroute A voice route includes a regular expression that identifies which phone numbers will be routed through a given voice route: phone numbers matching the regular expression will be routed through this route. This cmdlet verifies whether or not a given telephone number will be routed through a specified voice route based on the number pattern of the route (the NumberPattern property). You can use this cmdlet to troubleshoot routing issues or to simply try out phone numbers against specific routes to ensure the results are what you expect.
Published Date : Monday, September 25, 2017