WordPress Azure SSO, Blocks, APIs
Budget: $15 – $25 USD
My current WordPress install needs a security-first overhaul that authenticates every user through Microsoft Entra ID (Azure AD) Single Sign-On. I want the login flow to be completely hands-off once configured: new users provisioned automatically, existing roles mapped correctly, multi-factor respected, and all traffic forced through HTTPS/OAuth 2.0 / OIDC endpoints.
Beyond hardening access, I also have an editorial roadmap that relies on several custom Gutenberg blocks—think dynamic, reusable components that pull data from external services and match our brand styling perfectly. These blocks must be coded the WordPress-native way (no heavy page-builder hacks) so they remain fast, accessible, and fully compatible with future core updates.
A set of scheduled API integrations rounds out the brief. On a configurable cron schedule the site should call partner endpoints, cache JSON responses, and surface the data via those new blocks as well as a few custom REST routes. Reliability, error-logging, and graceful rollbacks are essential because missed updates directly impact what visitors see.
Deliverables
• Production-ready Microsoft Entra ID (Azure AD) SSO configured, documented, and tested
• Bespoke Gutenberg blocks (built with @wordpress/scripts, ESNext, JSX) wired to site styles
• WP-Cron (or Action Scheduler) jobs that fetch, store, and expose external API data
• Short README summarising setup steps, environment variables, and how to extend each component
Please include links or repo snippets from past projects that prove hands-on experience with Azure AD SSO in WordPress, custom block development, and automated API workflows; that evidence will weigh more than any written proposal.
Beyond hardening access, I also have an editorial roadmap that relies on several custom Gutenberg blocks—think dynamic, reusable components that pull data from external services and match our brand styling perfectly. These blocks must be coded the WordPress-native way (no heavy page-builder hacks) so they remain fast, accessible, and fully compatible with future core updates.
A set of scheduled API integrations rounds out the brief. On a configurable cron schedule the site should call partner endpoints, cache JSON responses, and surface the data via those new blocks as well as a few custom REST routes. Reliability, error-logging, and graceful rollbacks are essential because missed updates directly impact what visitors see.
Deliverables
• Production-ready Microsoft Entra ID (Azure AD) SSO configured, documented, and tested
• Bespoke Gutenberg blocks (built with @wordpress/scripts, ESNext, JSX) wired to site styles
• WP-Cron (or Action Scheduler) jobs that fetch, store, and expose external API data
• Short README summarising setup steps, environment variables, and how to extend each component
Please include links or repo snippets from past projects that prove hands-on experience with Azure AD SSO in WordPress, custom block development, and automated API workflows; that evidence will weigh more than any written proposal.