Merge pull request #877 from MicrosoftDocs/main

Publish main to live, 09/27, 11:00 AM IST

Planner/disable-planner-component.md

@@ -9,7 +9,7 @@ audience: Admin
 ms.topic: article
 ms.service: office-perpetual-itpro
 ms.subservice: planner
-ms.localization_priority: medium
+ms.localizationpriority: medium
 ---
 
 # How to turn off the Planner component for your organization

Planner/planner-limits.md

@@ -9,7 +9,7 @@ audience: Admin
 ms.topic: article
 ms.service: office-perpetual-itpro
 ms.subservice: planner
-ms.localization_priority: medium
+ms.localizationpriority: medium
 ---
 # Microsoft Planner limits
 

Project/delete-user-data-project-server-subscription-edition.md

@@ -6,7 +6,7 @@ manager: jtremper
 audience: ITPro
 ms.topic: article
 ms.service: project-server-itpro
-localization_priority: Normal
+localizationpriority: medium
 description: "Learn how a Farm admin can delete a specific user's data from a Project Server Subscription Edition environment."
 ms.date: 09/08/2021
 ---

ProjectOnline/periodic-tasks-for-project-online-administrators.md

@@ -22,38 +22,38 @@ description: "Describes periodic checks Project Online admins should perform to
 This article describes periodic checks Project Online admins should perform to maintain their environments.
 
 Project Online administrators should perform the following periodic checks to their environment as an important part of their job:
-  
-|**Daily**|
+
+| Daily |
 |:-----|
-|Check the queue for  *Failed and Blocking*  jobs.  <br/> |
-|Review the errors related to  *Failed and Blocking*  jobs to troubleshoot.  <br/> |
-|Cancel  *Failed and Blocking*  jobs.  <br/> |
-   
-|**Weekly**|
+|Check the queue for  *Failed and Blocking*  jobs. |
+|Review the errors related to  *Failed and Blocking*  jobs to troubleshoot. |
+|Cancel  *Failed and Blocking*  jobs. |
+
+| Weekly |
 |:-----|
-|Check Active Directory synchronization jobs to ensure they were successful.  <br/> |
-|Update Resource Breakdown Structure (RBS) values for new users. Newly synched users won't have an RBS.  <br/>  NOTE: This may be the job of the PMO.           |
-|Clear any overly long delegation sessions in Server Settings | Delete Enterprise Objects | User Delegation.  <br/> |
-|Maintain a valid enterprise resource pool by checking for users who haven't logged in for 60 days and find out why. For example, they may have left the company, are unaware of PWA, or could have been added mistakenly when someone else needed access.  <br/> |
-|Check the ADMINISTRATORS group for admins that should be removed.  <br/> |
-|Check for news on upcoming features or updates.  <br/> |
-   
-|**Monthly**|
+|Check Active Directory synchronization jobs to ensure they were successful. |
+|Update Resource Breakdown Structure (RBS) values for new users. Newly synched users won't have an RBS.  <br/>  NOTE: This may be the job of the PMO. |
+|Clear any overly long delegation sessions in Server Settings. Delete Enterprise Objects. User Delegation. |
+|Maintain a valid enterprise resource pool by checking for users who haven't logged in for 60 days and find out why. For example, they may have left the company, are unaware of PWA, or could have been added mistakenly when someone else needed access. |
+|Check the ADMINISTRATORS group for admins that should be removed. |
+|Check for news on upcoming features or updates. |
+
+| Monthly |
 |:-----|
-|Provide timesheet training to new users.  <br/> |
-|Provide project manager training to new project managers.  <br/> |
-|Check on license usage. For example, use data to follow up with users on licenses that are not being used.  <br/> |
-   
-|**Quarterly**|
+|Provide timesheet training to new users. |
+|Provide project manager training to new project managers. |
+|Check on license usage. For example, use data to follow up with users on licenses that are not being used. |
+
+| Quarterly |
 |:-----|
-|Close timesheet periods for the previous quarter plus one or some similar period. For example, if you are in Q4, close the timesheet reporting periods for Q2. The interval will be based on business or reporting needs.  <br/> |
-|Check with the project manager first, then close tasks to updates on projects that are complete or mostly compete or that have older tasks.  <br/> |
-|Delete timesheets from the past. Again, this will be defined by a policy that is based on business needs for reporting timesheet data.  <br/> |
-   
-|**Yearly**|
+|Close timesheet periods for the previous quarter plus one or some similar period. For example, if you are in Q4, close the timesheet reporting periods for Q2. The interval will be based on business or reporting needs. |
+|Check with the project manager first, then close tasks to updates on projects that are complete or mostly compete or that have older tasks. |
+|Delete timesheets from the past. Again, this will be defined by a policy that is based on business needs for reporting timesheet data. |
+
+| Yearly |
 |:-----|
-|Create fiscal periods for the next calendar year.  <br/> |
-|Create timesheet periods for the next calendar year. The prefix might equal "Week.", starting at 1, and the suffix might be the calendar year, such as ".2016". Week 1's period will show as "Week.1.2016".  <br/> |
-|Consider deleting timesheets for long-ago periods.  <br/> |
+|Create fiscal periods for the next calendar year. |
+|Create timesheet periods for the next calendar year. The prefix might equal "Week.", starting at 1, and the suffix might be the calendar year, such as ".2016". Week 1's period will show as "Week.1.2016". |
+|Consider deleting timesheets for long-ago periods. |