@Kris Robbins With v4.0 an explicit classification model is required for compose model if you are using multiple extraction models in the compose model. As per documentation:
The
2024-07-31-previewimplementation of themodel composeoperation replaces the implicit classification from the earlier versions with an explicit classification step and adds conditional routing.
So, with the current GA version that you are using, the composed model determines implicitly without the need of a custom classification model to generate a response that best matches one of the models in the composed model.
So, as per the composed model compatibility list your region can support composing v3.0 and v3.1 models in a composed model id without the need of training a custom classification model.
If you use a custom classification model with v3.0 you can still classify the document types and train a model. Based on the output of your classification model i.e the document type that is returned you will have to make another call to your custom extraction model id to analyze the document.
If you use v4.0 API in a different region you will have to follow the approach of creating a custom classification model with different document types and train the custom classification model and then train individual custom extraction models of the types used in custom classification and link them up in a compose operation i.e use the custom model classification model id, custom extraction model id's for all the types used in the custom classification model.
I am also not sure about ETA of launching v4.0 in Australia region. Please check the What's new page regularly for updates on future rollouts.
I hope this helps!!
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.