Update to Get-CsDialPlan, Get-CsOnlineUser, and Get-CsUserPolicyAssignment cmdlet in the Teams PowerShell Module [MC950879]

Update to Get-CsDialPlan, Get-CsOnlineUser, and Get-CsUserPolicyAssignment cmdlet in the Teams PowerShell Module [MC950879]

Message ID: MC950879

There are important changes coming to a few Teams PowerShell cmdlets. Starting January 2025, we will be deprecating Get-CsDialPlan cmdlet. We will also be deprecating DialPlan attribute from Get-CsOnlineUser and LocationProfile attribute from Get-CsUserPolicyAssignment cmdlet. If you are using DialPlan or LocationProfile attribute found in these cmdlets, please stop using them.

[How this will affect your organization:]

You are receiving this message because our reporting indicates your organization may be using Microsoft Teams Phone services. When this change is implemented,

  • Administrators will no longer be able to use Get-CsDialPlan cmdlet.
  • Administrators will no longer be able to get DialPlan from Get-CsOnlineUser cmdlets.
  • Administrators will no longer be able to get LocationProfile from Get-CsUserPolicyAssignment cmdlet.

DialPlan and LocationProfile are Microsoft internal use only attributes and we believe Microsoft Teams Phone administrators do not have any direct usage for these. To understand the effective dial plan please use: Get-CsEffectiveTenantDialPlan.

We will gradually roll out this change to customers in early January 2025, and we expect to complete by mid January 2025.

[What you need to do to prepare:]

This change will happen automatically, no admin action is required. Please notify your admins about this change, update relevant documentation and automations as appropriate.

Detailed instructions on these cmdlets are provided in Get-CsOnlineUser, Get-CsUserPolicyAssignment, Get-CsEffectiveTenantDialPlan.

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The upcoming changes to the Teams PowerShell Module, specifically the deprecation of the Get-CsDialPlan cmdlet, as well as the DialPlan and LocationProfile attributes from Get-CsOnlineUser and Get-CsUserPolicyAssignment, are certainly noteworthy. As we approach January 2025, both administrators and users will need to adapt to these updates, and the impact will vary across the board.

    For administrators, the removal of these cmdlets may initially seem daunting. Without the ability to access the DialPlan and LocationProfile attributes, admins will need to pivot and leverage the Get-CsEffectiveTenantDialPlan cmdlet instead. This change might feel like losing a favorite tool in the toolbox; however, it’s important to remember that these attributes were primarily for Microsoft’s internal use. Thus, the shift might streamline processes and reduce confusion in the long run. Plus, less clutter in the cmdlets could lead to a more efficient management experience—think of it as decluttering your workspace!

    For users, the direct impact may be less pronounced, but it’s still crucial to stay informed. While they may not be directly using these cmdlets, awareness of the changes can help in understanding any potential shifts in service delivery or support. It’s always good to be in the loop, right? After all, knowledge is power—even if it’s just knowing that your admin is no longer using a cmdlet they never understood in the first place!

    As we gear up for these changes, it’s essential to communicate with your teams, update documentation, and perhaps even share a chuckle or two about the joys of navigating tech updates. Change can be daunting, but it also opens the door to new opportunities for learning and growth.

    I encourage everyone to share their thoughts and experiences regarding these updates in the comments below. Have you faced similar changes in your organization? How do you feel about the transition? Let’s keep the conversation going! For more insights, check out additional posts on mwpro.co.uk.

Leave a Reply

Your email address will not be published. Required fields are marked *