FYI: A colleague just hit this exact same scenario
- There were no filters blocking access to resources; and we could see resources under the same subscription deployed to the same location, and could see that there were no filters on resource type
- Navigating directly to the resource's URI worked; as did running CLI and PWSH commands to list the resource.
- However any search for the resource (e.g. browsing resources under a resource group, using Azure search, or clicking the resource type through Azure search and looking at the list of resources of that type) did not show the new resource.
- Other users didn't have the same issue.
Our best guess is that this is caused by some kind of replication latency between nodes; and the user with the issue just happened to be hitting a node with an older cache. We're hoping the issue resolves itself as the day progresses & this cache refreshes.
We couldn't find a way to force that though. i.e. Logging out and back in, clearing browser cache, using incognito mode, and logging to the resource then searching for it after we've already found it, all failed to refresh these lists of resources.