About

We are seeking a skilled developer to build a simple Azure Maps PowerApps Component Framework (PCF) that integrates seamlessly with Model-Driven Apps and Power Pages. The ideal candidate will have experience with Azure Maps APIs and a strong understanding of Power Platform capabilities (such as core differences between what works in Model Drive Apps, and what renders on Power Pages). You will be responsible for creating a user-friendly component that enhances our application's mapping functionalities. A portfolio showcasing previous relevant work is highly desirable. We need a small, focused Power Apps PCF (code component) that: - renders an Azure Maps map, - watches address fields (line1/city/area/postcode/country,latitude,longitude), - geocodes as the user types (debounced), - writes latitude/longitude to bound fields and recenters the map, - runs in both Model-driven and Power Pages (Basic Form), - no draggable pin and full overwrite of address fields and lat/long desireable but not essential at this stage. Inputs/properties: - line1, city, area, postcode, country (bound) - latitude, longitude (bound, write outputs) - azureMapsKey (string) - autoGeocode (TwoOptions, default true) Tech notes: - Use Azure Maps Web SDK v3 (load lazily; reuse if already on window). - No hardcoded secrets; key must come from property. - No frameworks unless approved (prefer plain TS + PCF API). - Deliver source + unmanaged solutions + short setup guide (we will integrate/add into our main dynamics solution we use). Please share 1–2 portals-enabled PCF examples. Confirm you’ll meet the acceptance tests for both Model-driven and Power Pages.