/ Azure Architecture Consultant

Fortune 500 Ag Data Platform

Cloud-native field trial data for a global biosciences team

EnterpriseAzureAPIMAKSMicroservicesData Lake

portal.azure.com

Microsoft Azure

Search resources, services, and docs

Default Directory

Home › API Management services › apim-prod-eus2 › APIs

APIs

Filter by name…

⟳ Refresh ⤓ Export

Display name

URL suffix

Protocol

Revision

Subs

Calls / mo

internal-apis

/internal/v1

HTTPS

rev-3

1.4M

web-mobile-apis

/app/v2

HTTPS

rev-1

820K

partner-apis

/partners/v1

HTTPS

rev-2

210K

policies.xml · inbound ● applied

<inbound>
  <validate-jwt header-name="Authorization" failed-validation-httpcode="401">
    <openid-config url="https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration" />
  </validate-jwt>
  <rate-limit-by-key calls="60" renewal-period="60" />
</inbound>

/ THE STORY

The context

A Fortune 500 agricultural biosciences company runs thousands of crop product field trials globally — North America, China, India, Brazil. Data sources are fragmented across farm equipment, field management platforms, soil and tissue labs, satellite imagery, and legacy systems. The brief: unify all of it on Azure so agronomists and biostatisticians can actually use it.

My role

App Architect for the Azure platform layer — owning API Management (APIM) and shared C# microservices alongside a senior peer. Designed a three-product API governance model isolating internal systems, web/mobile frontends, and external partner integrations with independent rate limits, JWT validation, and audit. Pioneered a public-endpoint + IP-whitelisting pattern that unblocked enterprise networking constraints (corporate DNS forwarding restrictions) and prevented a multi-week architectural delay.

What it proves

I can architect Azure platforms at enterprise scale — API governance, multi-tenant identity, observable microservices — and ship through a Fortune 500's approval and infrastructure constraints.

/ HIGHLIGHTS