What’s New? Unveiling the Latest Features of the Azure Native Dynatrace Service
Introducing Multi-Subscription Monitoring for Dynatrace on Azure We’re excited to announce the general availability of Multi-Subscription Monitoring (MSM) for the Azure Native Dynatrace Service (ANDS). This powerful new capability allows customers to monitor multiple Azure subscriptions through a single Dynatrace resource—significantly simplifying the setup of observability for multiple Azure subscriptions at scale. Organizations often operate across dozens—or even hundreds—of Azure subscriptions. Until now, when setting up observability with the Azure Native Dynatrace Service, customers had to create one Dynatrace resource per Azure subscription, leading to higher operational overhead and some redundant configurations. With Multi-Subscription Monitoring, customers can now consolidate monitoring of up to 20 Azure subscriptions into a single Dynatrace resource, streamlining their operations and reducing complexity. 🧩 How It Works The feature is available directly in the Azure portal: Navigate to your Dynatrace resource. Go to Environment Configuration > Monitored Subscriptions. Click Add Subscriptions. Select the subscriptions you want to monitor—Dynatrace will automatically detect those where your managed identity has the required permissions. Click Add. Once added, the subscriptions will appear with an “Active” status, and diagnostic settings will be applied automatically based on your tag rules. ⚠️ Note: You can link up to 20 subscriptions per Dynatrace resource. If you reach the 20 subscriptions linked to one Dynatrace resource, you have to create a new Dynatrace resource in the next Azure subscription you want to link. To use MSM, the managed identity associated with your Dynatrace resource must have Owner permissions on the target subscriptions. 📘 Learn More Check out the article here for step-by-step guidance and stay tuned for updates on the Azure Tech Community blog. We look forward to your feedback! Announcing Enhanced Customization for Dynatrace OneAgent Installation on Azure VMs We’re excited to introduce a powerful new capability in the Azure Native Dynatrace Service: The installation of Dynatrace OneAgent on Virtual Machines (VMs) now supports additional parameters. This enhancement adds flexibility and control to your observability workflows—directly from the Azure portal. Previously, customers installing Dynatrace OneAgent via the Azure portal needed to manually configure important options. This included enabling system logs, choosing infrastructure-only monitoring, or setting proxy configurations. These settings were only available through CLI-based setups or post-installation. This manual configuration created friction for certain use cases, including the following: Security-conscious teams wanting to pre-configure log ingestion, proxy settings and custom installation paths. SREs managing multiple subscriptions desiring to predefine host groups and network zones for better organization and routing. With this update, we’re providing advanced configuration and automation. What’s New: Full Parameter Control at Install Time You can now configure the following parameters during agent installation via the Azure portal or CLI: Parameter Description Monitoring Mode Enable full-stack or infra-only monitoring Host Group Assign host to a logical group Network Zone Route traffic through a specific network zone Proxy Define address of proxy server Custom Host Name Custom host name for agent Enable Log Monitoring Enable/disable log monitoring Enable Auto Update Auto-update agent version Access to System Logs Enable/disable system log collection Enable Automatic Ingestion Enable/disable auto-ingestion Extensions ingest port Set custom ingest port StatsD Port Set custom StatsD port These parameters are optional, giving you the freedom to tailor the installation to your environment’s needs. 🔍 Learn More To explore the full list of parameters and their usage, check out the official Dynatrace documentation: Customize OneAgent installation on Linux — Dynatrace Docs We look forward to your feedback!
Partner Blog | Microsoft & Oracle: The future of enterprise cloud data for partners
In today’s fast-changing cloud and AI landscape, our partnership with Oracle represents the power of collaboration to drive customer transformation at scale. Microsoft and Oracle share a common goal: to enable organizations to modernize their data estates, accelerate AI innovation, and deliver measurable business outcomes. Oracle Database@Azure brings this vision to life by combining the best of both platforms and putting our partners at the center of that transformation. Announcements from Oracle AI World At Oracle AI World, we introduced a new set of advancements that expand what’s possible for our customers and partners. Azure Accelerate, within the Microsoft AI Cloud Partner Program, support now includes Oracle Database@Azure workloads, offering partners funding, credits, and the Cloud Accelerate Factory for zero-cost deployment assistance. This allows partners to move customers to Azure faster, reduce migration risks, and increase delivery speed. Partners will also be able to resell Oracle Database@Azure directly through Microsoft Marketplace, making it easier to package, license, and deploy solutions globally while building new revenue streams. The platform itself also continues to evolve quickly. Oracle Database@Azure now supports Oracle Base Database Service, Exadata Exascale 19c, and Oracle Database 23ai across more than 28+ regions worldwide, enabling a broad multicloud hyperscaler reach. Native Oracle GoldenGate integration with Oracle Database@Azure now connects directly to Microsoft Fabric, making it easier to unify data across systems, reduce latency, and activate AI and analytics at scale. Partners can also use Copilot Studio and Azure AI Foundry to create and deploy custom agents and low-code AI solutions powered by more than 1,900 models. Security and operations are integrated across Microsoft Defender, Sentinel, and Entra ID, giving customers AI-driven threat detection, real-time monitoring, and unified identity management. Azure Arc integration adds full visibility, policy management, and automation across hybrid and multicloud environments, allowing partners to deliver consistent governance from a single control plane. The partnership between Microsoft and Oracle builds on years of co-engineering, centered on helping customers modernize mission-critical workloads without compromise. Together, we’ve brought Oracle Exadata infrastructure directly into Azure datacenters, unifying Microsoft and Oracle ecosystems through shared networking, identity, and governance. The result is a seamless cloud experience that combines Azure’s scalability and security with Oracle’s trusted database performance. Continue reading here!Generate Now! Podcast - Agentic AI Partner and Industry Conversations
James Caton sits down with Microsoft industry experts and leading global system integrators (GSIs) to explore how Agentic AI is transforming industries— from banking and healthcare to manufacturing and public sector. Apple Podcasts Spotify Podcasts YouTube Channel Subscribe and listen on all major podcast platforms. Each episode will feature behind-the-scenes insights, measurable impact, and the strategic thinking that’s driving Agentic AI success at scale. Season SN Topic 2 1 Gaming Industry Agentic AI (Byung-su Kim, Microsoft) 2 2 Banking Industry Agentic AI (Daragh Morrissey, Microsoft) 2 3 Retail CPG Industry Agentic AI (Mike Edmonds, Microsoft) 2 4 Telco Industry Agentic AI (Rick Lievano, Microsoft) 2 5 Manufacturing Industry Agentic AI (Eleni Rachaniotou, Microsoft) 2 6 EY's Ed Bobrin on Agentic AI 2 7 PwC's Diego Jarne on Agentic AI 2 8 Capgemini's Roshan Gya on Agentic AI 2 9 NTTDATA's Charlie Doubek on Agentic AI 2 10 Infosys Mona Dash on Agentic AI 2 11 LTIMindtree Sheba Fernando on Agentic AI 2 12 EPAM Dmitry Tikhomirov on Agentic AI Connect with James at https://www.linkedin.com/in/jmcaton/Join the Movement at Azure Dev Summit!
Azure Dev Summit is a chance for you to join a community of developers, architects, and tech leaders building with Azure, .NET, and Microsoft AI. This isn’t just another conference. It is a Microsoft-sponsored celebration of innovation, learning, and connection — and we’re bringing some of the most inspiring voices in tech to the stage. Find out more about the speakers at Azure Dev Summit and make sure to register! https://azuredevsummit.com/Sora 2 now available in Azure AI Foundry
Sora 2 in Azure AI Foundry stands out by combining OpenAI’s most advanced video generation capabilities with the trusted infrastructure and security controls of Microsoft Azure. And through Azure AI Foundry and our responsible AI principles, we empower customers with embedded security, safety, and privacy controls. Azure AI Foundry offers a curated catalog of generative media models, including OpenAI’s Sora, GPT-image-1 and GPT-image-1-mini, Black Forest Lab’s Flux 1.1 and Kontext Pro, and more to empower developers in your and customer organizations to serve creatives with new and unique capabilities, all without sacrificing the safety, reliability, and integration businesses expect. Learn more here!Microsoft Partner Center account structure: Best practices for long-term success
About the author: David Starr is the founder and CEO of Cumulus26, where focus is on accelerating customer's Azure Marketplace journey from onboarding to business success. He is a former Principal Architect at Microsoft working on Azure Marketplace and a 6-time Microsoft MVP in Developer Tooling. Why account structure matters in Partner Center When first creating a Partner Center account, many Software Development Company (SDC) partners I’ve worked with dive straight into creating their transactable offers without first considering how their accounts are structured. This often leads to confusion about account setup, creating multiple “orphan” accounts, and support incidents that can delay the publication of your software to the Microsoft Marketplace--or even result in losing access to Partner Center. This article examines Partner Center account structures and the primary decisions to make when setting up your company’s accounts in the portal. We’ll cover the following. Initial considerations: Individual accounts. Understanding organizational account structures and configurations. Working with important identifiers used in account management and support scenarios. Setting up for long-term successful management of your accounts. This article ensures you’ll know how to structure your Microsoft Partner Center account so that it supports your organization’s needs today and can scale with you as you grow. Understanding Partner Center account management After initially creating your account, it’s tempting to skip user management and move on to other tasks in the portal. This can lead to the common mistake of failing to assign multiple account administrators right away. The predictable outcome is that if an account administrator leaves your organization, your staff could lose the ability to administer-- or even access-- Partner Center. This may sound intuitive upon reading it, so why mention it? It’s because I have worked with many publishers who failed to do this and were later unable to get the access they needed. This leads to time spent resolving support incidents, which can delay publishing your solution. Before diving into setting up an account, it’s helpful to understand there are three different accounts involved: Microsoft accounts, Azure Entra ID accounts, and Partner Center accounts. Although, the Microsoft account is essentially an extension of the Azure Entra ID account. In short, you must have an Azure Entra ID account to have a Partner Center account. These account types are shown in the image below. Each has its own features and capabilities. It is worth noting while you do need an Entra ID account, you do not need an Azure subscription, which allows creation of services like databases or virtual machines. This can be an important point for Azure administrators who provide accounts strictly for use with Partner Center. Setting up an Azure tenant in Partner Center Azure accounts for your organization are stored in tenants, which provide identity, security, and account management through Microsoft Entra ID. At least one tenant must be associated with Partner Center to manage the portal’s accounts. This allows those with accounts in the tenant to also have accounts in Partner Center. You may associate a pre-existing Entra ID account with Partner Center, or you may create one if needed. Regardless of which technique you use, you can manage users and permissions for Partner Center after configuring your tenant. User accounts After configuring your tenant, head over to the user management screen in Account settings, then select User management in the left side menu. As we mentioned earlier, the next account you’ll want to configure is another Global administrator. If you created the Azure tenant you are working with, you already have Global Administrator permissions in Partner Center. Otherwise, you may need to contact your Azure administrator to get the permissions you need. This is why it’s common (and good) practice for organizations with pre-existing Azure tenants to have an Azure administrator initially set up Partner Center. Adding another Partner Center administrator For this next step, there are three options for adding that new person to Partner Center: Create new user – Used if there are no other user accounts in the tenant. Add existing user – Use this if there are existing user accounts in the tenant. Invite outside user – May be used for inviting someone from outside your organization to manage Partner Center for you. Regardless of which method you choose, since you are adding a second Global administrator, give them that role during account setup. This is the first role listed in the account setup process as shown here. Configuring partner global and location accounts Now that you have at least two global administrators, you can turn your attention to setting up your organizational accounts. There are two types in Partner Center. Partner global account (PGA) Partner location account (PLA) Structuring your accounts There is one PGA per SDC and one or more PLAs. A PGA is an overarching account containing contact and other information for your organization. Each PLA account represents a different location for the organization. A single PLA is created when you first create a Partner Center account. This may be enough for some organizations, but for many SDCs it’s a good idea to consider how you will organize the company and its products in the future. See the image below for a typical example of PGA and PLA structures, the information associated with them, and their roles. Some organizations may want multiple PLAs to represent different sales centers or divisions within the SDC. It’s also a good idea for smaller SDCs to consider future growth at this stage. Think about how and where your company may eventually do business. However, you do not need multiple PLAs to sell your solution in multiple countries--you can sell worldwide even if you have only one PLA. Both PGAs and PLAs have unique identifiers, examples of which are shown in the below image. You may need to access these when working with Microsoft. To do so, go to: Account Settings > Identifiers > Microsoft AI Cloud Partner Program Managing publisher accounts and identifiers Each PLA has one or more publisher accounts, which are established when enrolling in the Microsoft Marketplace program. Each publisher also receives its own set of identifiers, and it’s common to be asked for these in customer support scenarios. When creating a new publisher, you get to specify your publisher account’s primary ID, but a second Seller ID is automatically assigned for you. To access publisher IDs, visit: Account settings > Identifiers > Publisher Tax and payment profiles-- used by Microsoft to bill on your behalf and to pay you for customer purchases-- are associated with publisher accounts. Publisher accounts are sometimes used by different billing departments or to organize products into logical groups. See the image below for a typical example. As you can see, the account structure is straightforward. If you consider it in advance of setting up Partner Center, you will be more likely to avoid configuration mistakes and be set up well for future growth. Organizing offers and plans for marketplace publishing We’ve seen how to structure user and organizational accounts to ensure a great Partner Center experience. When it’s time to set up your products to sell in the marketplace there are two more entities involved, offers and plans. Offers represent your base software product and plans are used to sell one or more SKUs of the product. For example, Cumulus26’s AMPup solution for marketplace publishers may be our offer, and has different plans for team, professional, and enterprise versions. To support global software sales, each plan is associated with one or more global markets. For example, a US-based publisher may sell software in Canada, the UK, and Germany. Selling markets are designated for each plan. Of course, each offer and plan receives its own ID. For each, you must specify the ID as you create each entity, and I recommend planning a logical naming convention for these IDs as you may need to navigate marketplace features using them at some point. Now you have a complete picture of Partner Center structures from PGAs all the way to plans as shown in the image below, which represents a single-region seller. This turns out to be the most common Partner Center account configuration due to its simplicity and the needs of most SDCs. Conclusion: Building for scalability and support There is a strong relationship between Microsoft Azure Entra ID and Partner Center accounts. For many SDCs the simplest path to successful user management is to start with an Entra ID Global Administrator setting up your initial Partner Center account. Don’t forget the important first step of adding a second Partner Center account administrator. You are now ready to model your organization and products in Partner Center, from PLAs and PGAs to offers and plans. You also understand the ID structures of each entity. You can refer to this article for help on where to find them when needed. With a solid understanding of Partner Center user and organizational account structures, you are ready to begin configuring your users and organization in Partner Center. To learn more and ask questions, attend the How to structure your Microsoft Partner Center account for long term success | Microsoft Community Hub session on November 4th. If you are unable to attend, the session will be recorded for viewing after.
