Address missing description metadata

Author: andrewconnell

docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md

@@ -1,7 +1,8 @@
 ---
 title: Guidance - Migrate from classic workflows to Power Automate flows in SharePoint
+description: This article specifically provides guidance about how to plan for transitioning from classic SharePoint Workflows to Power Automate flows.
 ms.date: 07/21/2020
-search.app: 
+search.app:
   - Flow
 search.appverid: met150
 ---
@@ -54,9 +55,9 @@ To learn more about building workflows using Power Automate in SharePoint, start
 ## Pain points in moving between classic workflows in SharePoint and Power Automate flows
 
 Many people feel there are significant gaps between SharePoint Designer (classic) workflows and Power Automate flows, but the list is not long. Of course, there are some workarounds you should consider in your planning as you move from classic workflows to Power Automate flows.
-	
+
 - **30 day run limit for flows** – SharePoint Designer workflows can run endlessly, but flows have a 30 day lifespan. Getting beyond this limitation means your flow will need to call itself in a re-entrant way to restart the clock ticking.
-- **HTTP Connector** – If you make calls to SharePoint's REST API, then you can use  the ['Send HTTP Request to SharePoint'](../guidance/working-with-send-sp-http-request.md) action available in the SharePoint connector. Flow also has a generic HTTP connector (as an action), but it is a Premium connector. If you use HTTP calls extensively, you may want to create a “service account” user with a Power Automate license and run these flows with that user account. This also will make it easier to manage the set of flows you consider "enterprise" flows. 
+- **HTTP Connector** – If you make calls to SharePoint's REST API, then you can use  the ['Send HTTP Request to SharePoint'](../guidance/working-with-send-sp-http-request.md) action available in the SharePoint connector. Flow also has a generic HTTP connector (as an action), but it is a Premium connector. If you use HTTP calls extensively, you may want to create a “service account” user with a Power Automate license and run these flows with that user account. This also will make it easier to manage the set of flows you consider "enterprise" flows.
 - **Reusable Flows** – Using some modular thinking, you can create a master flow which a flow per list or library can call to do the heavy lifting. (In some ways this is even preferable, as you can edit a flow which is used in many locations centrally.) Alternatively, you can use flow actions to discover all of the lists or libraries which match some criteria and run the flow on them all on a timer rather than based on events.
 - **Workflow history storage** – Flows maintain a history in the context of the flow itself in the Power Automate dashboard. If you need tracking in your sites, you can have the flow log information in a list you create.
 - **Impersonation** - In SharePoint 2010 workflows, you can add an impersonation step to act as a different user. This capability is not readily available in flows.

docs/general-development/accessibility-in-sharepoint.md

@@ -1,5 +1,6 @@
 ---
 title: Accessibility in SharePoint
+description: Learn about the features, products, and services that make SharePoint accessible for people with disabilities, and find developer resources that can help you design and build apps and websites that support key accessibility scenarios.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: c9106d47-c523-49c1-b9f1-cdd7420abd5e

docs/general-development/changes-in-the-bdc-model-schema-for-sharepoint.md

@@ -1,5 +1,6 @@
 ---
 title: Changes in the BDC model schema for SharePoint
+description: Learn what has changed in SharePoint for the BDC model schema.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: 882ea867-9acb-4313-99c9-865a523b72fd

docs/general-development/common-error-messages-in-sharepoint-workflow-development.md

@@ -1,5 +1,6 @@
 ---
 title: Common error messages in SharePoint workflow development
+description: A listing of common error messages that you might encounter while developing SharePoint workflows and guidance for solving the underlying problem.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: e9bf6878-c722-4b1f-b5b5-b302ae0ea4da

docs/general-development/how-to-use-the-subcode-property-to-capture-error-codes.md

@@ -1,5 +1,6 @@
 ---
 title: Use the SubCode property to capture error codes
+description: Excel Services generates errors in the SOAP exception based on errors that occur in Excel Services. To make it easier for the developer to catch specific error conditions, an Excel Calculation Services alert has an associated error code.
 ms.date: 09/25/2017
 keywords: how to,howdoi,howto,subcode
 f1_keywords:

docs/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md

@@ -1,5 +1,6 @@
 ---
 title: SharePoint Add-ins compared with SharePoint solutions
+description: Learn about when to develop your SharePoint extension as a SharePoint Add-in and when to develop it as a SharePoint farm solution or a no-code sandboxed solution.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: 0e9efadb-aaf2-4c0d-afd5-d6cf25c4e7a8

docs/general-development/site-collection-app-catalog.md

@@ -1,5 +1,6 @@
 ---
 title: Use the site collection app catalog
+description: Using site collection app catalogs, SharePoint tenant administrators can decentralize the management and scope the deployment of SharePoint add-ins and SharePoint Framework solutions to specific sites.
 ms.date: 09/07/2020
 ms.prod: sharepoint
 ms.assetid: fdf7ecb1-9951-475b-b058-3285fba77b68

docs/general-development/virtual-directories-in-sharepoint-solutions.md

@@ -1,5 +1,6 @@
 ---
 title: Virtual directories in SharePoint solutions
+description: Learn about how changes in the virtual directory system affect how you create farm solutions in SharePoint.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: c26c4160-31be-4358-89cf-082b8a1e6a6c

docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md

@@ -1,5 +1,6 @@
 ---
 title: What's new for developers in social and collaboration features in SharePoint
+description: Learn about new and changed social and collaboration features for My Site and Community Site development scenarios in SharePoint.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: 65365b1d-cde5-47cd-8b04-1b76be0e3490

docs/general-development/workflow-initiation-and-configuration-properties.md

@@ -1,5 +1,6 @@
 ---
 title: Workflow initiation and configuration properties
+description: See an overview of the initiation and association properties that SharePoint sets on workflows.
 ms.date: 09/25/2017
 ms.prod: sharepoint
 ms.assetid: 7386bbf9-3ed6-4732-bcdb-b27baed7397e
@@ -13,8 +14,6 @@ See an overview of the initiation and association properties that SharePoint set
 > [!NOTE]
 > SharePoint 2010 workflows have been retired since August 1, 2020 for new tenants and removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more info, see [SharePoint 2010 workflow retirement](https://support.microsoft.com/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f).
 
-## 
-
 When you launch a workflow, SharePoint automatically sets a number of association and initiation properties that support the workflow. These are listed below. The set of properties that are set differs slightly depending whether it is a **site** workflows or a **list** workflow. These differences are identified in the lists.