Purview on-demand classification "cost-estimation" still in progress!

With ImpactAssessmentInvalid, no completion timestamp and almost two weeks without progress, I’d open a Microsoft support case now rather than assume the estimate is still processing.

The fields shown don’t establish that the job is active: IsEstimationStopped : False only says it isn’t marked stopped, and empty ErrorMetadata doesn’t prove success. I wouldn’t interpret ImpactAssessmentInvalid as a normal intermediate state without confirmation from Microsoft.

For the scale questions, keep these distinctions separate:

• 250 million total files versus 80 million matching files: don’t assume the filters make the job compliant with the 100-million limit. The important question is whether that limit applies before or after filtering, and whether estimation has its own enumeration constraints. Ask support to confirm this for your configuration.
• Estimation versus classification: don’t apply an auto-labelling daily limit to this workflow unless Microsoft explicitly documents it. These are different operations.

Provide the scan identifier, full configuration, PowerShell output, UTC start time and portal screenshots. Ask support to check the backend job state, last successful processing activity, and whether the scope was rejected or exceeded a service limit.

Preserve those details before cancelling or recreating the job. A smaller, non-overlapping site scope could be a useful diagnostic test, but wouldn’t explain or repair the original job by itself.