Azure Automated ML Batch Endpoint Spacy 3.7.4 compatibility issue

 If you tried to create a Batch Endpoint on Azure ML Studio and receive an error like the one shown below, the solution is provided in this blog post. If you need any assistance, feel free to reach out to blog@aileronconsulting.com.

=========================================================

#10 401.7 The conflict is caused by:
#10 401.7     The user requested spacy==3.7.4
#10 401.7     en-core-web-sm 3.4.1 depends on spacy<3.5.0 and >=3.4.0
#10 401.7 
#10 401.7 To fix this you could try to:
#10 401.7 1. loosen the range of package versions you've specified
#10 401.7 2. remove package versions to allow pip attempt to solve the dependency conflict
#10 401.7 
#10 401.7 
#10 401.7 failed
#10 401.7 
#10 401.7 CondaEnvException: Pip failed

=========================================================

The issue is in the environment file and the package en_core_web_sm-3.4.1 is not compatible with spacy 3.7.4.

Reach out (blog@aileronconsulting.com) if you would like to create custom environment that uses en_core_web_sm-3.7.1, which is compatible with the spacy package and use this base image  https://mcr.microsoft.com/azureml/curated/ai-ml-automl-dnn-gpu:21.

  

Azure Front Door with Wildcard domains

 When setting up Azure Front Door with wildcard domain names, there are a few things that need to be taken care of to get everything working correctly. Here are some key steps -

1. Add your domain.
   
2. Create the Origin Group / Origin. When creating the Origin leave the Origin Host Header blank. If you have a Private Link to, say, a backend load balancer, then enable that as well.
   
   
   
   
3. In your Front Door Endpoint, add the route to your wildcard domain.
   
   
   
   
4. Since you would need to create a CNAME to point to the endpoint, use HTTP Forwarding from your DNS server (or DNS provider) for your naked domain to, say, www.whateveryourdomainis.com. Then create a CNAME for www to point to the Endpoint.
   
   
   
   
   If you have any questions, please reach out to blog@aileronconsulting.com. We are happy to assist.

blog@aileronconsulting.com