Added ToC entry for How to schedule indexers article. Also linked to the article from the four tech-specific indexer articles.

Author: RobDixon22

articles/search/TOC.yml

@@ -163,24 +163,26 @@
     items:
     - name: Indexers overview
       href: search-indexer-overview.md
-    - name: Blob storage indexer
-      href: search-howto-indexing-azure-blob-storage.md
-    - name: Table storage indexer
+    - name: Azure Table Storage indexer
       href: search-howto-indexing-azure-tables.md
-    - name: SQL DB indexer
+    - name: Azure SQL DB indexer
       href: search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md
-    - name: Cosmos DB indexer
+    - name: Azure Cosmos DB indexer
       href: search-howto-index-cosmosdb.md
-    - name: One-to-many blob indexing
-      href: search-howto-index-one-to-many-blobs.md
-    - name: CSV blob indexing
-      href: search-howto-index-csv-blobs.md
-    - name: JSON blob indexing
-      href: search-howto-index-json-blobs.md
-    - name: Connect to SQL Server VMs
-      href: search-howto-connecting-azure-sql-iaas-to-azure-search-using-indexers.md
+    - name: Azure Blob Storage indexer
+      items:      
+      - name: Set up a Blob Storage indexer
+        href: search-howto-indexing-azure-blob-storage.md
+      - name: Index one-to-many blobs
+        href: search-howto-index-one-to-many-blobs.md
+      - name: Index CSV blobs
+        href: search-howto-index-csv-blobs.md
+      - name: Index JSON blobs
+        href: search-howto-index-json-blobs.md
     - name: Field mappings
       href: search-indexer-field-mappings.md
+    - name: Connect to SQL Server VMs
+      href: search-howto-connecting-azure-sql-iaas-to-azure-search-using-indexers.md
     - name: Troubleshooting common issues
       href: search-indexer-troubleshooting.md
   - name: Enrich with AI

articles/search/search-howto-connecting-azure-sql-database-to-azure-search-using-indexers.md

@@ -154,23 +154,7 @@ You can also arrange the indexer to run periodically on a schedule. To do this,
 
 The **interval** parameter is required. The interval refers to the time between the start of two consecutive indexer executions. The smallest allowed interval is 5 minutes; the longest is one day. It must be formatted as an XSD "dayTimeDuration" value (a restricted subset of an [ISO 8601 duration](https://www.w3.org/TR/xmlschema11-2/#dayTimeDuration) value). The pattern for this is: `P(nD)(T(nH)(nM))`. Examples: `PT15M` for every 15 minutes, `PT2H` for every 2 hours.
 
-The optional **startTime** indicates when the scheduled executions should commence. If it is omitted, the current UTC time is used. This time can be in the past – in which case the first execution is scheduled as if the indexer has been running continuously since the startTime.  
-
-Only one execution of an indexer can run at a time. If an indexer is running when its execution is scheduled, the execution is postponed until the next scheduled time.
-
-Let’s consider an example to make this more concrete. Suppose we the following hourly schedule configured:
-
-    "schedule" : { "interval" : "PT1H", "startTime" : "2015-03-01T00:00:00Z" }
-
-Here’s what happens:
-
-1. The first indexer execution starts at or around March 1, 2015 12:00 a.m. UTC.
-2. Assume this execution takes 20 minutes (or any time less than 1 hour).
-3. The second execution starts at or around March 1, 2015 1:00 a.m.
-4. Now suppose that this execution takes more than an hour – for example, 70 minutes – so that it completes around 2:10 a.m.
-5. It’s now 2:00 a.m., time for the third execution to start. However, because the second execution from 1 a.m. is still running, the third execution is skipped. The third execution starts at 3 a.m.
-
-You can add, change, or delete a schedule for an existing indexer by using a **PUT indexer** request.
+For more information about defining indexer schedules see [How to schedule indexers for Azure Search](https://docs.microsoft.com/en-us/azure/search/search-howto-schedule-indexer).
 
 <a name="CaptureChangedRows"></a>
 

articles/search/search-howto-index-cosmosdb.md

@@ -279,6 +279,8 @@ This indexer runs every two hours (schedule interval is set to "PT2H"). To run a
 
 For more details on the Create Indexer API, check out [Create Indexer](https://docs.microsoft.com/rest/api/searchservice/create-indexer).
 
+For more information about defining indexer schedules see [How to schedule indexers for Azure Search](https://docs.microsoft.com/en-us/azure/search/search-howto-schedule-indexer).
+
 ## Use .NET
 
 The generally available .NET SDK has full parity with the generally available REST API. We recommend that you review the previous REST API section to learn concepts, workflow, and requirements. You can then refer to following .NET API reference documentation to implement a JSON indexer in managed code.

articles/search/search-howto-indexing-azure-blob-storage.md

@@ -116,6 +116,8 @@ This indexer will run every two hours (schedule interval is set to "PT2H"). To r
 
 For more details on the Create Indexer API, check out [Create Indexer](https://docs.microsoft.com/rest/api/searchservice/create-indexer).
 
+For more information about defining indexer schedules see [How to schedule indexers for Azure Search](https://docs.microsoft.com/en-us/azure/search/search-howto-schedule-indexer).
+
 ## How Azure Search indexes blobs
 
 Depending on the [indexer configuration](#PartsOfBlobToIndex), the blob indexer can index storage metadata only (useful when you only care about the metadata and don't need to index the content of blobs), storage and content metadata, or both metadata and textual content. By default, the indexer extracts both metadata and content.
@@ -139,7 +141,6 @@ Depending on the [indexer configuration](#PartsOfBlobToIndex), the blob indexer
   * **metadata\_storage\_last\_modified** (Edm.DateTimeOffset) - last modified timestamp for the blob. Azure Search uses this timestamp to identify changed blobs, to avoid reindexing everything after the initial indexing.
   * **metadata\_storage\_size** (Edm.Int64) - blob size in bytes.
   * **metadata\_storage\_content\_md5** (Edm.String) - MD5 hash of the blob content, if available.
-  * **metadata\_storage\_sas\_token** (Edm.String) - A temporary token that can be used by [custom skills](cognitive-search-custom-skill-interface.md) to get right access to the blob. This sas token is not supposed to be stored for later use as it may expire.
 * Metadata properties specific to each document format are extracted into the fields listed [here](#ContentSpecificMetadata).
 
 You don't need to define fields for all of the above properties in your search index - just capture the properties you need for your application.

articles/search/search-howto-indexing-azure-tables.md

@@ -111,6 +111,8 @@ This indexer runs every two hours. (The schedule interval is set to "PT2H".) To
 
 For more information on the Create Indexer API, see [Create Indexer](https://docs.microsoft.com/rest/api/searchservice/create-indexer).
 
+For more information about defining indexer schedules see [How to schedule indexers for Azure Search](search-howto-schedule-indexer.md).
+
 ## Deal with different field names
 Sometimes, the field names in your existing index are different from the property names in your table. You can use field mappings to map the property names from the table to the field names in your search index. To learn more about field mappings, see [Azure Search indexer field mappings bridge the differences between datasources and search indexes](search-indexer-field-mappings.md).
 

articles/search/search-howto-schedule-indexers.md

@@ -109,7 +109,3 @@ The .NET SDK lets you control indexer operations using the [SearchServiceClient]
 You can run an indexer on demand at any time using one of the [Run](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.search.indexersoperationsextensions.run), [RunAsync](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.search.indexersoperationsextensions.runasync), or [RunWithHttpMessagesAsync](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.search.iindexersoperations.runwithhttpmessagesasync) methods.
 
 For more information about creating, updating, and running indexers, see [IIindexersOperations](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.search.iindexersoperations?view=azure-dotnet).
-
-
-## Help us make Azure Search better
-If you have feature requests or ideas for improvements, please reach out to us on our [UserVoice site](https://feedback.azure.com/forums/263029-azure-search/).