![Update to Get-CsPhoneNumberAssignment [MC950880]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-steve-27578998-1024x683.webp)
Message ID: MC950880
To maintain the best performance and reliability of our service, we are updating the page size limit for the phone number retrieval API (Get-CsPhoneNumberAssignment cmdlet) to a maximum of 1,000 numbers per query.
[When this will happen:]
General Availability (Worldwide, GCC): We will begin rolling out early January 2025 and expect to complete by mid-January 2025.
[How this will affect your organization:]
From January 6, 2025, any request with -Top parameter exceeding 1,000 will result in a "Bad request." Please ensure that your Get-CsPhoneNumberAssignment requests do not surpass this limit. If the intended operation is to export your numbers, please use https://learn.microsoft.com/en-us/powershell/module/teams/export-csacquiredphonenumber?view=teams-ps
[What you need to do to prepare:]
Please ensure that your Get-CsPhoneNumberAssignment requests do not surpass this limit.
Source: Microsoft
![Viva Engage reactions history data will soon be available in network-level data export. [MC950877]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-417344-150x150.webp)
![Microsoft Teams: Forward messages to and from channels [MC950897]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-harrisonhaines-2869565-150x150.webp)
The recent update to the Get-CsPhoneNumberAssignment cmdlet is set to create quite a ripple in the world of phone number management, and it’s worth taking a moment to assess how this will impact both admins and users alike.
For admins, this change means a shift in how phone number retrieval requests are handled. The new page size limit of 1,000 numbers per query is a significant adjustment. While it may seem like a limitation at first, it actually promotes better performance and reliability. Think of it as a speed limit that, when followed, keeps the traffic flowing smoothly instead of causing a jam. Admins will need to adjust their scripts and processes to ensure that requests stay within this new boundary. However, with a little planning, they can easily adapt and continue to manage phone number assignments effectively.
On the user side, the impact is likely to be less pronounced. Most users won’t notice the change unless they’re involved in the nitty-gritty of number assignments or exports. For those who do, it’s a gentle reminder to keep an eye on the quantity of numbers being queried. After all, nobody enjoys hitting a “Bad request” wall!
As for the overall impact, this update is a step toward enhancing system performance, which is always a win in the tech world. It encourages better practices and helps avoid the pitfalls of large data requests that can bog down systems. So, while it may require a bit of adjustment, the long-term benefits are undoubtedly worth it.
Now, let’s turn the floor over to you, dear readers! What are your thoughts on this update? Do you foresee any challenges, or do you think it’s a positive move? Share your insights in the comments below! And for those seeking more information, don’t forget to check out additional posts at mwpro.co.uk. Let’s keep the conversation going!