Share via

Deployment of azure farmbeats application get failed.

Karan Chauhan 1 Reputation point
2021-12-14T05:52:24.223+00:00

The pre-requsite powershell script cannot register the app using azurewebsites.net domain and keeps fauling with the error, "HostNameNotOnVerifiedDomain".
this article explains why the azurewebsites.net domain can nolonger be used to register new app uri's since the 15-Oct-2021. See https://learn.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains

The poweshell script succeeds by editing create_aad_script-1.2.12.ps1 to replace azurewebsites.net with a valid AAD domain.

Running the farmbeats install specifying a valid AAD domain app uri (as above) fails after 30mins because the install requests azurewebsites.net domain even though the a valid AAD domain registered app uri is specified.
it appears that the farmbeats install is hard coded to use the azurewebsites.net domain irrespective of the registered apps uri domain specified during the install.

thus, the install will only succeed if the registered app uri uses the azurewebsites.net uri which cannot work since 15-Oct-2021.

We need solution on this problem as soon as possible.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,850 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. AshokPeddakotla-MSFT 29,396 Reputation points
    2021-12-15T15:11:32.31+00:00

    @Karan Chauhan We regret for the inconvenience caused. As mentioned, we have notified this issue to our team and below is an update.

    You are trying to setup the Azure FarmBeats version which is in public preview. We want to update you on the new version of FarmBeats which we are building. It’s a fully managed PaaS offering (Platform-As-A-Service). The rearchitected PaaS platform makes it easy for customers to use FarmBeats, here are a few advantages:

    Simple onboarding: You don’t have to provision multiple resources under your tenant. Just instantiate the PaaS version of the FarmBeats, and we will take care of all the complexity behind the scenes
    Improved scalability and performance: PaaS service will take care of scaling and provides better performance (Ex: faster ingestion of satellite data in seconds)
    More features: PaaS version supports data related to satellite imagery, weather, Farm operations, Sensors (WIP), event notifications, and more. It natively supports agronomic constructs like farms, fields, seasons, crops, management zones, prescription maps, etc.
    Extensibility: There will now be no limitation to work with an approved list of weather service or sensor providers. The extensibility framework can help customers to work with any weather service and sensor providers (WIP) of their choice in FarmBeats.
    Out-of-the-box AI/ML models: FarmBeats supports a few out of the box AI/ML/Statistical models like sensor placement map, biomass estimation model, Soil moisture map, boundary identification, NDVI forecast, LAI, etc. which can be leveraged by users
    Power analytics: PaaS version has developer-friendly Python SDK. Users can create ARDs easily using APIs and build/train their AI/ML/Statistical models on Azure

    In case you want to use the new version of FarmBeats, kindly write to us at FarmBeatsSupport [at] microsoft [dot] com by providing your Azure subscription ID and GitHub ID to get access to the product documentation. Also, note that the new version does not have a UI layer. It is to be used via APIs only.

    Hope this helps. Do let us know if you have any further queries.

    -------------------------

    If an answer is helpful, please click on 130616-image.png or upvote 130671-image.png which might help other community members reading this thread.

    0 comments