Merge pull request #171503 from HeidiSteen/heidist-quickfix

[azure search] Add indexer troubleshooting item for Azure sql serverless

Author: PRMerger9

articles/search/search-indexer-troubleshooting.md

@@ -8,7 +8,7 @@ author: mgottein
 ms.author: magottei
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 06/27/2021
+ms.date: 09/07/2021
 ---
 
 # Indexer troubleshooting guidance for Azure Cognitive Search
@@ -58,6 +58,12 @@ The `AzureCognitiveSearch` service tag can be directly used in the inbound [NSG
 
 More details for accessing data in a SQL managed instance are outlined [here](search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers.md)
 
+## Azure SQL Database serverless indexing (error code 40613)
+
+If your SQL database is a on a [serverless compute tier](../azure-sql/database/serverless-tier-overview.md), make sure that the database is running (and not paused) when the indexer connects to it.
+
+If the database is paused, the first login from your search service will auto-resume the database, but it will also return an error stating that the database is unavailable with error code 40613. After the database is running, retry the login to establish connectivity.
+
 ## SharePoint Online Conditional Access policies
 
 When creating a SharePoint Online indexer you will go through a step that requires you to sign in to your Azure AD app after providing a device code. If you receive a message that says `"Your sign-in was successful but your admin requires the device requesting access to be managed"` the indexer is likely being blocked from accessing the SharePoint Online document library due to a [Conditional Access](../active-directory/conditional-access/overview.md) policy.