Operations | Monitoring | ITSM | DevOps | Cloud

At CloudZero, we talk to leadership teams at SaaS and companies every day. When it comes to individual customer profitability, the vast majority of them fall into two camps: they’re either taking their best guess — or they have no idea. Typically only the largest companies - those with the resources to dedicate a 5-10 person engineering team to calculating cost - have this level of insight. And you can be sure they yield that knowledge to their competitive advantage!

In the previous article, we have created the Continuous Integration (CI) pipeline for a simple Java application. It is now time to start working on the Continuous Deployment (CD) pipeline that will take the Java application and deploy it to AWS. To build the CD pipeline, we will extend the existing AWS Jenkins pipeline. If you have missed the previous article on building a CI pipeline for a Java application using Jenkins, make sure you read that first before continuing.

Do you need to integrate a new company in with your existing employer and therefore in to your already provisioned Azure AD tenant. Or perhaps just need to share your tenancy and office 365 services with more than one company, then you could find yourself in a position where you need to sync users from another domain and have already configured AD Connect, well there is a way to add the second domain to your current Azure tenancy, so you can sync those users from the second domain.

If there’s no customer, there’s no job. In a competitive marketplace, every site element matters from the functionality of your service to your UI; your documentation to your marketing. Your SLA should mirror that structure. Building a strong customer experience is about consistency on every level. The key is visibility, offering all the verification your customers need with an intuitive click of the mouse.