INTEGRATE 2025 Day 2 Highlights

#1: Enhancing Developer Effectivity with Logic Apps

The session led by Wagner Silvera, Senior Product Supervisor at Microsoft, targeted on enhancing the developer expertise for Azure Logic Apps. Right here’s a concise abstract of the important thing factors mentioned:

Introduction and Agenda:

Wagner launched the session by emphasizing the significance of enhancing the developer expertise in Logic Apps. The agenda included discussions on workspaces, unit testing, customized elements, and the brand new “code for workflows” characteristic.

Workspaces:

• Workspaces are actually a central characteristic in Azure Logic Apps, permitting builders to handle a number of sources in a single place.
• A prescribed construction for organizing code helps in producing deployment scripts and managing customized code successfully.
• A prescribed construction for organizing code helps in producing deployment scripts and managing customized code successfully.

Migrating Present Initiatives:

• For current Logic Apps initiatives, a migration course of is on the market to transition to the brand new workspace paradigm with out shedding current configurations.
• A cloud-to-local characteristic permits builders to import Logic Apps from the Azure portal into their native improvement atmosphere seamlessly.

Automated Testing Framework:

• The session launched a unit testing framework particularly designed for Logic Apps, permitting builders to check workflows successfully.
• The session launched a unit testing framework particularly designed for Logic Apps, permitting builders to check workflows successfully.
• The framework helps mocking exterior dependencies, permitting for remoted testing of workflow logic.

Customized Code and Scripting:

• The session highlighted the mixing of customized code inside Logic Apps, permitting builders to put in writing inline scripts in languages like C# and PowerShell.
• Enhancements within the customized code expertise embrace the flexibility to herald exterior packages and dependency injection, enhancing the pliability of Logic Apps.

Code for Workflows:

• This new characteristic permits builders to create workflows utilizing an crucial programming mannequin, combining code with the prevailing declarative workflow mannequin.
• This new characteristic permits builders to create workflows utilizing an crucial programming mannequin, combining code with the prevailing declarative workflow mannequin.

Operational Capabilities:

• The mixing of code for workflows maintains the operational capabilities of Logic Apps, permitting for monitoring, logging, and debugging throughout the similar software.

Future Plans:

• The session concluded with a preview of upcoming options and enhancements, together with the overall availability of customized code and enhanced unit testing capabilities.

General, the session emphasised Microsoft’s dedication to enhancing the developer expertise in Azure Logic Apps by means of enhanced tooling, higher testing frameworks, and the mixing of coding capabilities, making it simpler for builders to construct and handle workflows successfully.

#2: Assist! My Azure invoice simply retains getting greater

This session by Michael Stephenson – a FinOps licensed practitioner and Microsoft MVP addresses the pervasive drawback of escalating Azure prices, highlighting that many organizations, of their rush to undertake cloud applied sciences, usually overlook the essential facet of value sustainability. He emphasizes that a good portion of cloud spending, estimated at 20-30%, is wasted as a result of a scarcity of visibility, disconnect between roles, and absence of accountability. He advocates for cultivating a cost-aware tradition the place everybody understands their contribution to the Azure invoice and actively seeks to maximise worth whereas minimizing waste.

Integration Initiatives: A Prime Instance of Price Fluctuation

The session delves into the particular challenges of managing prices in integration initiatives, noting that not like the fastened prices of on-premise options, cloud-based integration companies usually have consumption-based pricing fashions that may result in unpredictable value fluctuations. Companies like Logic Apps and Operate Apps, whereas providing flexibility, can incur variable prices relying on load and processing necessities. Stephenson factors out the shocking rarity of cost-related non-functional necessities (NFRs) in initiatives, suggesting that incorporating value targets can considerably shift the mindset and drive extra cost-conscious selections.

Turbo360: A Device for Price Optimization

To deal with these challenges, Stephenson proposes a sensible, iterative method to FinOps, beginning with gaining visibility into value knowledge, analyzing key value drivers, monitoring for anomalies, after which optimizing useful resource utilization. He introduces Turbo360 as a instrument to facilitate this course of, providing options equivalent to value evaluation dashboards, budgeting and monitoring capabilities, rightsizing suggestions, reservation administration, and scheduling for automated useful resource scaling.

The session additionally options James Reed from West Coast Cloud, who shares how they leverage Turbo360 as a prospecting instrument, offering potential prospects with a report highlighting cost-saving alternatives of their atmosphere. This permits them to current a concrete plan for value discount, demonstrating tangible worth and constructing belief.

Lastly, Stephenson makes use of the analogy of a backyard for example the significance of ongoing value administration, emphasizing the necessity for a “gardener” to keep up a wholesome cloud atmosphere. He outlines key “gardening” actions, together with eliminating unused sources, monitoring for value creep, mitigating surprising spend, and optimizing useful resource utilization.

In the end, the session argues that efficient Azure value administration is not only about saving cash, but in addition about liberating up sources to put money into innovation. By turning waste into worth, organizations can fund new initiatives, equivalent to AI, and drive enterprise development. Stephenson concludes by offering sources for additional studying, together with the Turbo360 YouTube channel, Azure on Air podcast, FinOps on Azure podcast and a price administration playbook. The core message is that by taking a proactive and strategic method to Azure value administration, organizations can regain management of their cloud spending, optimize useful resource utilization, and unlock the total potential of the cloud.

#3: Occasion pushed purposes with Azure Messaging

Right here’s a abstract of the session on event-driven architectures with Azure Messaging, that includes Clemens Vasters and Roberto Cervantes:

Roberto Cervantes (Occasion Grid):

• Occasion Grid Evolution: Occasion Grid is evolving past a standard push-delivery occasion dealer, integrating pull supply, an MQTT dealer, and extra.
• Webhooks and Net: Occasion Grid presents varied sources like system subjects, domains, customized subjects, and accomplice subjects. Occasion Grid Namespaces (normal tier) introduce versatile consumption fashions, enabling each push and pull mechanisms. Personal Hyperlink help is on the market for consuming occasions from personal locations.
• MQTT Dealer: Occasion Grid now features a extremely scalable, low-latency, and safe MQTT dealer, facilitating communication between units and purposes.
• Business Use Circumstances: Predictive upkeep, safety, distant monitoring, and linked environments are key areas. New patterns like many-to-one and one-to-many are rising.
• Sparkplug B: Occasion Grid helps Sparkplug B, a protocol utilized in industrial IoT for environment friendly message packaging and transmission.
• Unified Namespaces: The idea of unified namespaces goals to create a single supply of fact by connecting good purposes by means of an outlined construction, leveraging Sparkplug B.
• AMQP: Azure is dedicated to bringing AMQP help to public preview, aiming for standardization, reliability, and safety.
• Material Integration: A brand new connector in Material’s real-time hub permits publishing to Occasion Grid namespaces and connecting to Material for constructing highly effective options (e.g., automotive fleet options).
• What’s New in Occasion Grid: Investments in safety, cross-tenant eventualities, community safety perimeter integration, managed id help for webhooks, OpenID Join suppliers for MQTT, dynamic authentication utilizing webhooks/Azure Features, and assigned consumer identifiers.
• Coming Quickly: Common Availability (GA) for public preview options, AMQP help, retain HTTP publish, bulk API for gadget registration, elevated message measurement for MQTT, and shared subscriptions.

Demo:

• A simulation of commercial IoT units utilizing Occasion Grid with MQTT dealer enabled.
• Sparkplug B protocol used for sending/receiving messages.
• Subscription to obtain MQTT messages in a webhook, with knowledge despatched to Material, Occasion Stream, and Occasion Hub.
• Demonstrated bidirectional communication between purposes utilizing MQTT.

Clemens Vasters (Metadata and Messaging):

• Unified Namespace (revisited): Formalizing the unified namespace idea utilizing X Registry to seize machine standing messages with assigned paths.
• Metadata Significance: Emphasizing the necessity for schemas to enhance knowledge high quality and make clear intent, particularly for AI purposes.
• Cloud Occasions: An ordinary for outlining occasions and their protocol bindings (cloudevents.io).
• X Registry: An extensible registry for metadata, endpoints, schemas, and message metadata, offering a proper method to format streams and outline schemas for knowledge in pipelines (xregistry.soaphub.org).
• MCP XReg: A short lived website (mcpxreg.com) with X Registry plugins and fashions for agent card suppliers, API suppliers, and container registries, aiming to construct a uniform message metadata graph.
• JSON Construction: A proposed IETF Web draft (json-structure.org) to repair the issues of JSON Schema by simplifying it, offering a greater sort system, and providing annotations for scientific models and currencies.

Key Takeaways:

• Azure Messaging is evolving to help numerous event-driven eventualities, together with IoT and real-time knowledge processing.
• MQTT and AMQP have gotten more and more essential protocols.
• Metadata and schemas are essential for knowledge high quality and AI purposes.
• X Registry and JSON Construction are initiatives to enhance metadata administration and knowledge definition.

#4: Classes from the frontlines: Actual-world success with Azure API Administration throughout Safety, Governance, and AI

The session focuses on widespread patterns noticed in API administration throughout varied prospects, highlighting real-world examples and discussing Azure’s investments on this space. The audio system – Anish Tallapureddy and Alex Vieira emphasize the growing significance of API administration as a result of rising complexity and sprawl of APIs, particularly with the rise of AI.

Key Factors:

• API First Strategy: Many enterprises are adopting an API-first method to enhance agility, allow parallel improvement, and shift safety left. Moneris, a fintech firm, was cited for example of an organization that has adopted an API first method as a part of their enterprise mannequin.
• Microservices and Modernization: Modernizing legacy purposes with microservices and containers presents challenges in managing APIs at scale. Zeiss, a multinational firm, was talked about for example of an organization that has adopted containers and frameworks like Dapr, and leverages Azure API administration so as to expose these APIs.
• SaaS Integration: Integrating with varied SaaS options requires safe connectivity, token administration, and observability. Gucci, an organization from Switzerland, was talked about for example of an organization that leverages Azure API administration, so as to present its connectivity layer with help for all knowledge and different protocols.
• Low Code/No Code Integration: Enterprises are utilizing low-code platforms like Energy Apps to construct UIs rapidly, with API Administration performing as a bridge between pro-code and low-code improvement. Tokyo Metro was cited for example of an organization that has adopted an structure that describes the relation between the professional code and the low code.
• Occasion-Pushed Architectures: Actual-time knowledge and the necessity for techniques to react to occasions are driving the adoption of event-driven architectures. Mercedes Benz was cited for example of an organization that wishes to modernize the best way that they had been dealing with the autos.
• AI and APIs: APIs are essential for accessing AI fashions and integrating AI into current workloads. D-ID, an organization that’s constructing avatars very simply, was cited for example of an organization that’s implementing Azure API administration, in order that when a sure person entry to the APIs, the APIs are being uncovered by means of Azure API administration.
• Developer Expertise: Azure is investing in enhancing the developer expertise by means of AI-powered authoring, schema-first workflows, and integrations with instruments like VS Code and GitHub.
• API Safety: Safety is a prime precedence, with Azure providing options like Defender for APIs, safety insurance policies, and credential-less entry.
• Self-Hosted Gateway: The self-hosted gateway is a essential part for extending API administration to varied environments, together with on-premises, different clouds, and Kubernetes.
• Enterprise Outcomes: A Forrester research signifies a 315% ROI with Azure API Administration over three years, pushed by accelerated time to market and diminished integration prices.

#5: What’s new with Integration Atmosphere and Enterprise Course of Monitoring?

Kent Weare and Divya Swarnkar introduced updates on optimizing operations inside Azure Integration Companies (AIS). The presentation coated integration atmosphere updates, enterprise course of monitoring, and the usage of operational brokers to enhance productiveness.

Integration Atmosphere Updates (Divya):

• Alerting and Monitoring Enhancements: The main focus is on simplifying and streamlining the alert creation course of throughout the integration atmosphere, offering a unified expertise throughout Azure integration companies.
• Simplified Alert Creation: As an alternative of navigating Azure Monitor’s multi-step course of, customers can now create alerts instantly throughout the integration atmosphere.
• Really useful Alert Guidelines: The system gives pre-defined, beneficial alert guidelines primarily based on widespread buyer wants and telemetry evaluation, with customizable thresholds. These can be found for Logic Apps, API Administration, and Service Bus.
• Bulk Alert Creation: Alerts might be created for a number of sources (e.g., a number of Logic App workflows) concurrently.
• Software Well being Dashboard: An aggregated view of software well being, displaying the variety of alerts fired and their severity. Clicking on alerts gives detailed insights and troubleshooting choices.
• Message Tracing: A singular correlation ID (operation ID) flows throughout AIS sources, enabling end-to-end message tracing. Customers can visualize the journey of a message throughout Logic Apps, API Administration, and many others.
• Bulk Resubmission: Failed Logic App runs might be resubmitted in bulk from the monitoring dashboards.
• B2B/EDI Monitoring with Premium Integration Account: Help for B2B and EDI monitoring has been added to the premium tier of integration accounts.
• Azure Knowledge Explorer (ADX) for B2B Monitoring: Monitoring knowledge is saved in ADX for reliability and low latency, offering close to real-time telemetry for B2B options.
• Extensible Dashboards: Dashboards are primarily based on workbooks, making them extremely extensible to fulfill distinctive enterprise wants. Customers may also construct customized Energy BI dashboards utilizing the information in ADX.
• B2B Monitoring ID: A brand new non-obligatory subject in Logic Apps permits customers so as to add customized enterprise knowledge to trace, filter, and search messages.
• Demo of EDI Dashboard: Though there was a permission difficulty through the stay demo, the presenter described the dashboard’s capabilities, together with a high-level view of errors by accomplice and the standing of AS2/X12 EDI processing.

Enterprise Course of Monitoring (Kent Weare):

• Enterprise Stakeholder Engagement: Enterprise course of monitoring permits customers to mannequin enterprise processes, join them to technical implementations (Logic Apps), and supply enterprise stakeholders with visibility into course of standing.
• Azure Knowledge Explorer (ADX) for Enterprise Course of Monitoring: Knowledge is revealed to ADX for pace and reliability.
• Extensibility: Helps extension utilizing Energy BI or Azure Monitor workbooks.
• CICD Help (GA Launch): Introduces CICD help, making options transportable. Customers can export a deployed enterprise course of to a zipper file containing ARM templates and pipelines. An up to date Azure DevOps market activity helps combine enterprise course of monitoring with Logic Apps CI pipelines.
• Demo: Confirmed the design floor for modeling enterprise processes, defining knowledge properties, and mapping them to Logic App workflows utilizing the token picker. Demonstrated each profitable and failed paths, with deep hyperlinks to the underlying Logic App runs.
• Extensibility Examples: Confirmed examples of consuming enterprise course of monitoring knowledge in Energy BI and utilizing Azure workbooks. Talked about an alert template for enterprise course of monitoring that sends alerts on failures.

Operational Brokers (Kent Weare):

• SRE Agent: Leverages AI to enhance productiveness and scale back imply time to revive (MTTR). The SRE agent analyzes useful resource teams, identifies points, and gives proactive or reactive help.
• Integration with Azure Monitor: Alerts raised in Azure Monitor are surfaced within the SRE agent console, offering a centralized view of points.
• Root Trigger Evaluation and Suggestions: The agent performs root trigger evaluation, gives diagnostic findings, and suggests beneficial actions.
• Finest Follow Identification: The agent can establish alternatives to enhance useful resource configurations (e.g., recommending TLS 1.2).
• Agent Loop: A framework for orchestrating complicated operational processes utilizing a mixture of instruments, workflows, connectors, actions, and information.
• Data-Pushed Automation: Agent Loop can ingest info from operational runbooks (e.g., wikis, SharePoint paperwork) and use it to drive enterprise processes.
• Demo: Demonstrated a state of affairs the place Agent Loop helps resolve a blocked billing code difficulty in an ERP system. The agent interacts with a enterprise person through Groups to unblock the code, resubmits the Logic App run, and updates ServiceNow.

Name to Motion:

• Hyperlinks to the Enterprise Course of Monitoring GA weblog put up and in-product documentation had been supplied.
• Suggestions is requested on integration atmosphere monitoring through a survey.

#6: Improve API developer productiveness and speed up API adoption with Azure API platform

This session by Sreekanth Thirthala Venkata, Alex Vieira and Kristof Van Tomme focuses on enhancing developer productiveness utilizing the Azure API Administration platform, highlighting key challenges within the API improvement lifecycle and demonstrating options with Azure’s companies and AI-driven instruments.

Key Dialogue Factors:

• API Developer Lifecycle Challenges: The audio system establish challenges equivalent to issue in API discovery, making certain design normal compliance, API safety, model management, and documentation consistency.



• Azure API Administration and API Heart: They introduce Azure API Administration as a mature service for processing API transactions and the API Heart for central governance and monitoring of APIs.



• AI-Powered Options: The presentation showcases how AI, significantly GitHub Copilot, streamlines API discovery, design, and coverage creation. Demos embrace utilizing Copilot to search out current APIs, generate new compliant APIs, and create rate-limiting insurance policies.



• Finish-to-Finish Demo State of affairs: An order processing API is constructed, secured, and revealed utilizing obtainable market APIs. The demo covers designing the API, securing it with OAuth utilizing the purposes characteristic, and customizing the developer portal.
• API Safety with Purposes Characteristic: The newly launched purposes characteristic in restricted public preview is demonstrated, enabling API entry authorization utilizing OAuth tokens without having validated JWT token insurance policies.
• Developer Portal Customization: The presentation demonstrates customizing the developer portal with HTML widgets and customized pages to enhance the developer expertise.
• Monitoring and Observability: The audio system focus on investments in monitoring and observability, together with the Website Reliability Engineering (SRE) agent, to make sure API gateway reliability and automate incident administration.

Key Takeaways:

• Azure API Administration, mixed with AI instruments, considerably accelerates API improvement and enhances developer productiveness.
• The purposes characteristic simplifies API safety by enabling OAuth-based authorization.
• Customizable developer portals and accomplice options present flexibility to fulfill particular organizational wants.
• Monitoring and observability instruments are essential for sustaining API reliability and optimizing efficiency.

#7: Improve API developer productiveness and speed up API adoption with Azure API platform

The session targeted on securing and scaling APIs utilizing Azure API Administration, significantly with the AI Gateway. Andrei Kamenev and Julia Kasper mentioned the challenges in constructing AI-powered purposes, equivalent to safety, monitoring AI consumption, and making certain security. They highlighted the AI Gateway as an answer to those challenges, providing options like token price limiting, utilization monitoring, and content material security integration. The session additionally coated the Mannequin Context Protocol (MCP) and the way Azure API Administration is integrating with it to simplify the event and administration of AI-powered purposes.

Key Takeaways:

• OpenAI Appropriate APIs Help: The AI Gateway now helps all OpenAI appropriate APIs, no matter their deployment location (Azure or elsewhere).



• Responses API Help: Added help for Responses API, a brand new sort of API from OpenAI.
• Content material Security Integration GA: Content material Security integration is now usually obtainable, permitting customers to combine AI APIs with content material security options to detect and block dangerous content material.
• Semantic Caching GA: Semantic caching is now usually obtainable, enabling the AI Gateway to return completions from the cache for semantically related prompts, optimizing workload and lowering token prices.
• Amazon Bedrock API Help: The AI Gateway now helps Amazon Bedrock API, permitting customers to convey cloud fashions deployed on Amazon into API Administration with out altering their developer expertise.
• AI Gateway Launch Channel: A brand new launch channel is launched in API Administration portal, permitting customers to obtain new options as quickly as they’re shipped to manufacturing.
• Logs and Prompts Completion Logging: Launched logs and prompts completion logging to gather prompts and completions, which might be damaged down into a number of entries in the event that they exceed the utmost measurement restrict.
• REST APIs to MCP Servers: Now you can remodel your REST APIs into MCP servers.



• Azure API Heart Integration: Azure API Heart is now a part of the Azure API Administration product portfolio, serving as a list and registry for APIs and MCP servers.

#8: Efficient API governance within the period of AI with Azure API Administration

Right here is the glimpse of the session by Mike Budzynski and Mark Weitzel on API governance with API Administration.

Key Themes:

• Federated API Administration: The core idea is empowering API groups with autonomy whereas sustaining centralized oversight from a platform workforce. This entails decentralizing API administration with out shedding governance.
• Azure Companies Enabling Federated API Administration: The session focuses on three predominant Azure companies: Azure API Administration, Azure API Heart, and Azure Coverage.
• Microsoft Defender for Cloud: Making use of federated API safety throughout API administration companies.

Azure API Administration – Workspaces:

• Workspaces as a Key Characteristic: Workspaces allow federated API administration by offering management aircraft isolation, non-obligatory API runtime isolation, and API platform workforce controls.
• Management Aircraft Isolation: Workspaces act like folders with assigned permissions, isolating API groups.
• Elective API Runtime Isolation: Workspaces might be related to devoted or shared gateways, permitting for workload segregation and improved safety/reliability.
• API Platform Group Controls: Platform groups can implement runtime insurance policies throughout workspaces, implement federated logging, and preserve a centralized developer portal.
• Shared Workspace Gateway: Permits associating as much as 30 workspaces with a single gateway for value optimization.
• Federated Logging: Platform groups have central visibility into logs throughout all workspaces, whereas API groups solely see their very own workspace logs.
• Gateway Metrics and Auto Scale: Gateways now help CPU and reminiscence metrics, enabling auto-scaling primarily based on these metrics or schedules.
• Regional Help: Workspaces are increasing to extra areas, together with West Europe.
• Premium v2 Help: Workspaces are actually obtainable in Premium v2 (programmatic entry initially, UI help coming quickly).
• Roadmap: Customized hostnames, managed identities, and Defender for Cloud integration are deliberate for workspaces.

Azure API Heart:

• Federated API Stock: API Heart permits federating API stock from varied areas (Azure, AWS, different clouds) and lifecycle phases.
• Metadata Help: Helps metadata to higher construction and arrange the API stock for discovery and governance.
• API Design Compliance: Allows defining and imposing API design rule units, with integration into Visible Studio Code for shift-left compliance.
• AI Integration: Integrates with GitHub Copilot to facilitate API creation (e.g., OpenAPI specs).
• API Discovery: Facilitates discovery of APIs throughout options, clouds, deployment areas, and lifecycle phases.
• Integration with API Administration: The free tier of API Heart will likely be perpetually free with an API Administration Service. The usual tier of API Heart will likely be included with API Administration Customary or Premium.

Azure Coverage:

• Imposing Finest Practices: Azure Coverage permits implementing greatest practices, safety controls, and configuration controls throughout API Administration companies and APIs.
• Constructed-in and Customized Insurance policies: Helps built-in coverage definitions and customized coverage definitions for particular use instances.
• Enforcement and Auditing: Insurance policies can implement compliance on new sources or flag/audit compliance for current sources.

Microsoft Defender for Cloud:

• Federated API Safety: Gives superior API safety for APIs, particularly in managing API Administration companies.
• Menace Detection: Makes use of machine studying fashions to detect threats in close to real-time.
• API Safety Posture Evaluation: Discovers unauthenticated, externally uncovered, delicate, or dormant APIs.
• API Safety Posture in Defender CSPM: API safety posture evaluation is included in Defender CSPM.
• Discovery of API Led Assault Paths: Maps APIs to backend companies to grasp potential affect of API breaches.
• Discovery of Unmanaged APIs: Will uncover APIs throughout Azure App Companies (Operate Apps, Logic Apps, Net Apps) to establish doubtlessly susceptible APIs.

What’s New in API Administration:

• The API administration workforce has been including capabilities throughout varied components and eventualities of the product.
• Federated API administration of workspaces, making API administration clever with varied Copilots.
• Enhancements to validate Azure AD token and validate JWT insurance policies.
• Enhancements to Defender.
• Premium v2 preview with digital community injection, in addition to personal hyperlink capabilities.
• Making API administration extra person pleasant to builders and, making our builders simpler and extra environment friendly.
• AI capabilities, together with the gateway, together with MCP servers.
• Extra capabilities to API Heart and the cataloging experiences throughout API Engine and API Heart.

Coming Quickly:

• Service Bus Integration: API Administration will permit managing Service Bus queues and subjects as APIs, enabling insurance policies, observability, and safety.
• SAP Integration: API Administration can entrance SAP APIs, making use of insurance policies, observability, safety, and governance controls.

General Message:

The session highlights the shift in direction of federated API administration and the instruments and companies Azure gives to help this method. The main focus is on empowering API groups whereas sustaining centralized governance, enhancing safety, and enabling higher API discovery and administration. The presenter emphasised the continual enhancements and new options being added to Azure API Administration and associated companies.