Share via

A link was retired while the content is still meaningful.

Diana Balan 20 Reputation points Microsoft Employee
2026-03-09T06:38:39.8066667+00:00

The Project Server Boundaries we used to rely on (https://docs.microsoft.com/en-us/office/troubleshoot/project/expect-when-calling-into-paid-support) has meanwhile been retired in spite of the product still being in support.

Can we have it brought back?

Looking forward to your action of resurfacing this content.

Best Regards

Diana

Microsoft 365 and Office | Project | Other | Other
Microsoft 365 and Office | Project | Other | Other

Microsoft project management software used to plan, manage, and communicate a project schedule and other information among workgroup members, project managers, and other stakeholders.

0 comments No comments

Answer accepted by question author
  1. Henry-N 11,990 Reputation points Microsoft External Staff Moderator
    2026-03-09T07:51:52.4633333+00:00

    Hi @Diana Balan

    Thank you for posting your question in the Microsoft Q&A forum. 

    Regarding a content has been retired and you want to bring it back. 

    I agree that having this documentation available would be helpful for many customers, especially when troubleshooting or validating support expectations. 

    However, as a forum moderator, I do not have the ability to restore, update, or change official Microsoft documentation. Those decisions are made by the Microsoft Product teams, and the best way to request that this content be resurfaced is to submit feedback directly to them. 

    The most effective path is to send your suggestion through the official Microsoft Feedback Portal: 

    1. Visit the Microsoft Feedback Portal  Project · Community 
    2. Click “Send feedback”. 
    3. Describe your request clearly for example:  “Please reinstate the retired ‘Project Server Boundaries’ documentation, as the product remains in support and this content is still needed for troubleshooting.” 

    User's image

    The product team regularly reviews customer submitted feedback, and many documentation updates are driven directly by what users request. 

    As forum moderators, we don’t have the ability to change or override Teams product design or feature limitations, but we’re always happy to clarify current behavior and guide you to the appropriate feedback channels.   

    Thank you again for your time and understanding. While this response may not provide an immediate workaround, I hope it clearly explains what is and isn’t currently possible.    


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".             

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread    

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-09T06:38:49.89+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The retired article at that URL can’t be restored or its content reproduced here. When Microsoft documentation is retired, the owning product team decides whether to redirect, replace, or permanently remove it.

    For current, supported limits and boundaries, use the latest product documentation instead of the retired “Project Server Boundaries” article. For Project for the web, the supported limits are documented under “Project for the web boundaries,” which includes task, project, and resource limits such as maximum hierarchy levels, total tasks per project, and supported date ranges.

    If specific boundary information for Project Server or Project Online is still required and not covered in the current documentation, the only available path is to open a support request so the product team can advise or update live docs as needed.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.