Validation failed
This topic describes scenarios that can cause the validation to fail. After the issue has been corrected, you should run the validation process again to verify that all issues have been corrected.
There are no known validation failures. However, the Evaluate status may be displayed for some resources.
Schema exists in the target tenant as a different type
If a schema in the package already exists in the target tenant as a different type, the resource cannot be overwritten in the target. The import fails for the resource. For example, if a resource in the package is a JSON object schema and in the target tenant, the same resource already exists as a DSV object schema.
To correct this issue, you can delete the existing resource in the target tenant. If you do not delete the resource, the resource that is included in the package is not deployed to the target tenant. All other resources that do not have issues are imported.
Schema extension is in use by another schema file
If a schema extension that is included in the package uses a different schema file in the target tenant, then the Evaluate status is returned. In that case, before you proceed with the deployment, you must acknowledge the warning. If the extension is no longer required in the target tenant, you can remove it from the tenant before you proceed with the deployment. If you do not remove the schema extension from the target tenant, the extension in the file is skipped and is not imported.
Stream pipeline exists and is running in the target tenant
If a stream pipeline in the package already exists and is running in the target tenant, the resource cannot be overwritten in the target. The import fails for the stream pipeline.
To correct this issue, you can stop the existing stream pipeline in the target tenant. If you do not stop the stream pipeline, the resource that is included in the package is not deployed to the target tenant. All other resources that do not have issues are imported.
Stream pipeline exists in the target tenant with a different object name
If a stream pipeline in the package already exists in the target tenant and it has a different object name, the object name of the resource cannot be overwritten in the target tenant. This is because the object name cannot be changed on a stream pipeline that was active at least once. The import is successful but the stream pipeline object name is not updated.
To correct this issue, you can delete the existing stream pipeline in the target tenant. If you do not delete the stream pipeline, the resource that is included in the package is deployed but the object name is not updated. All other resources that do not have issues are imported.