Operations | Monitoring | ITSM | DevOps | Cloud

Suppose you are a user of the Microsoft integration stack, and your organization also uses SAP. In that case, you will likely have use cases where an IDOC triggers integration processes in SAP being published. One of the good things about Logic Apps on Azure is that a connector for SAP allows you to register to receive IDOCS published by SAP, and you can then use them in your integration processes.

Network topology can get very complicated in the cloud, especially when you’re sending data to external SaaS providers. You will likely need to configure gateways and firewalls and keep close tabs on those points of egress. However, if your infrastructure exists within AWS, there’s a much simpler way and that’s through an AWS PrivateLink endpoint.

If you have arrived at this page but need a quick refresher on what Azure Active Directory is and why it is different to Active Directory that you might have installed on-premises, you might like to first read this quick run-down – What is Azure Active Directory.

Organizations around the globe recognize the importance of digital transformation to respond to the demands of the modern world. Organizations can advance their business by adapting technology, processes and tools. By doing so, they can increase flexibility, efficiency, security and improve customer experiences to boost success and gain competitive advantage. However, digital transformation is not always easy.

I find it amazing how much opportunity and flexibility cloud environments are creating for organizations of all sizes. I’m seeing more and more companies experimenting with open-source software (OSS) relational database systems, which years ago would’ve been too complicated for the customer to set up. With Azure, you can spin up OSS systems like MySQL or PostgreSQL quickly to determine if the engine fits their needs. If it does, you can continue development on it.

If you have decided to move your infrastructure and workloads to the cloud, you know that there is no one-click shortcut for carrying out the migration process. There are multiple factors and particularities of your infrastructure to consider when planning and subsequently taking the necessary steps for cloud adoption.

To optimize its cloud investments, your organization needs internal stakeholders to act on shared knowledge about its cloud costs and cloud usage. But in practice, it’s difficult for organizations to gain a high degree of clarity about their cloud spending. The factors contributing to cost data are not normally visible to all stakeholders, and it’s often impossible to attribute costs to the teams, services, and applications that incurred them.

Microsoft's Azure and Amazon Web Services (AWS) are the two most popular cloud providers today. They both offer a variety of Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS) solutions. In addition, you'll find products covering multiple computing areas, such as compute, storage, analytics, and networking. You can also deploy AWS or Azure services in the cloud, on-premises, or as a hybrid setup.

Kubernetes has broken down barriers as the cornerstone of cloud-native application infrastructure in recent years. In addition, cloud vendors offer flexibility, speedy operations, high availability, SLAs (service-level agreement) that guarantee your service availability, and a large catalog of embedded services. But as organizations mature in their Kubernetes journey, monitoring and optimizing costs is the next stage in their cloud-native transformation.