Cannot update scan filter for ADLS Gen2 data source - getting HTTP 400 error

Question

I am using this API endpoint to update the scan filter of an ADLS Gen2 data source to exclude some URL prefixes:
https://learn.microsoft.com/en-us/rest/api/purview/scanningdataplane/filters/create-or-replace?view=rest-purview-scanningdataplane-2023-09-01&tabs=HTTP

It worked before, but recently it has started returning a 400 HTTP error. I have tried several previous API versions. The only thing that works is sending a request with an empty excludeUriPrefixes list, which successfully removes previously existing filters. Here are my request and response details:

Request body:

{ 	
	"properties": { 		
		"excludeUriPrefixes": [ 			
			"https://nameofmydatalake.dfs.core.windows.net/path1",
			"https://nameofmydatalake.dfs.core.windows.net/path2",
			"https://nameofmydatalake.dfs.core.windows.net/path3",
			"https://nameofmydatalake.dfs.core.windows.net/path4",
 			"https://nameofmydatalake.dfs.core.windows.net/path5"
 		],
 		"includeUriPrefixes": []
 	}
}

Response:

{
	"type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
	"title": "Bad Request",
	"status": 400,
	"traceId": "xx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxx-xx"
}

Answer 1

Hello SnurovasAleksandras-3884,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others (Opens in new window or tab)", I'll repost your solution in case you'd like to "Accept (Opens in new window or tab)" the answer.

Issue: Purview- Cannot update scan filter for ADLS Gen2 data source

Error: HTTP 400 error

Solution:

Adding a single "https://nameofmydatalake.dfs.core.windows.net" item to the includeUriPrefixes list in the request fixed the issue.

Example:

{
  "properties": {
    "includeUriPrefixes": [
      "https://foo.file.core.windows.net/share1/user"
    ],
    "excludeUriPrefixes": [
      "https://foo.file.core.windows.net/share1/user/temp"
    ]
  }
}

If you have any other questions or are still running into more issues, please let me know.
Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Answer 2

After some more tinkering, it seems like adding a single "https://nameofmydatalake.dfs.core.windows.net" item to the includeUriPrefixes list in the request fixed this.