Azure Search未识别到Azure SQL数据库的Integrated Change Tracking

I’ve seen this exact issue a few times when deploying Azure Search services across different regions—let’s walk through the most likely causes and how to fix them:

1. Permissions are missing for the new Search service #

Your existing Search service probably has the right permissions to check your SQL DB’s change tracking metadata, but the new one doesn’t. Azure Search needs two key permissions to verify ICT status:

• VIEW CHANGE TRACKING on the specific table you’re indexing
• VIEW DATABASE STATE on the database itself

If you’re using SQL authentication, run these commands on your Azure SQL database:

GRANT VIEW CHANGE TRACKING ON [YourTargetTable] TO [YourSearchSQLUser];
GRANT VIEW DATABASE STATE TO [YourSearchSQLUser];

If you’re using managed identity, head to your Azure SQL database’s Access Control (IAM) pane, assign the Contributor role (or a custom role with the above permissions) to your new Search service’s managed identity. Give it 5-10 minutes for permissions to propagate—this delay is easy to miss!

2. Regional metadata sync lag #

Since your new Search service is in a different region, there might be a delay in your SQL DB’s ICT status metadata being synced across Azure’s regional infrastructure.
First, confirm ICT is actually enabled by running these queries on your SQL DB:

-- Check table-level ICT
SELECT name, is_change_tracking_enabled 
FROM sys.tables 
WHERE name = 'YourTargetTable';

-- Check database-level ICT
SELECT is_change_tracking_enabled 
FROM sys.databases 
WHERE name = 'YourDatabaseName';

Both should return 1. If they do, wait 15-30 minutes and try creating the indexer again—regional sync can take a bit longer than you’d expect.

3. Subtle differences in data source configuration #

Double-check that your new data source setup matches the existing one exactly:

• Are you using the same connection method? (Managed identity vs. SQL auth connection string) A switch here can cause the indexer to query metadata differently.
• Did you select the correct table? Typos or case sensitivity (if your SQL DB uses a case-sensitive collation) can make the indexer check a table that doesn’t have ICT enabled.

4. Temporary regional service glitch #

Occasionally, regional issues with Azure Search or SQL can throw off metadata detection. Check the Azure Service Health dashboard in your portal to see if there are any ongoing outages or degradation in your new region. If there is, wait for the issue to resolve and try again.

Once you’ve worked through these steps, the indexer should recognize that Integrated Change Tracking is enabled, just like your existing service does.

内容的提问来源于stack exchange，提问作者Stpete111