Forum Discussion

arifsyeduk1's avatar
arifsyeduk1
Helper I
4 years ago
Solved

Azure Auto ML and Power BI

Hi, I have used Azure Auto ML to build a model and have deployed it successfully. I can also use the Test function that sits under the Endpoint option for my model.     I now wish to call t...
  • arifsyeduk1's avatar
    4 years ago

    Hi,

    this is the latest relpy I have from MS on this. Tbh, I'm not what the Swagger things is for, but looks like an underlying bug that MS are now investigating.

     

    *************

    I’ve downloaded the same data from Kaggle and built a classification model with that. It looks like the input schema is not being generated for scoring purposes. Here’s the documentation for the scoring script and how it needs to be formatted for schema generation: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-deploy-advanced-entry-script#automatically-generate-a-swagger-schema

     

    About a month or so ago, the product team added a new parameter to the script to return the predicted probabilities for classification tasks. This ask came from customer feedback wanting to deploy a model and get the underlying probabilities, not just the label. As you see in the following picture, a parameter called “method” is in the JSON test script. I think versioning the classification model’s scoring script has affected the model consumption method with the form editor. I’ve raised the issue to the product team; they’re investigating now.

     

     

     

    Meanwhile, I’ve built a regression model with the same data. On the AML test page, I can see the form editor now. When I connect this model with PBI, I can match the PBI dataset with the model attributes. The outputs are numeric, but you can set a threshold to convert the numeric results into categorical values. I believe that’s the quickest fix for now. I’ll keep you informed as soon as I hear an accurate answer/timeline to fix the bug for the classification models.

     

    ****************