New Simplified Azure Resource Metric Monitoring from AzureServiceMon

For those of you who missed our beta release announcement, AzureServiceMon is a new service from the company that brought you Office365Mon. We have just released a significant new addition to the service this week, which we call Azure Metric Monitoring.

When AzureServiceMon released beta 1, we provided availability monitoring and notifications for a number of your Azure resource types. It’s all wrapped up in a simple to use interface that regularly inventories your collection of Azure resources so as you change what you’re using, you don’t need to try and keep your monitoring in sync. One of the first pieces of feedback we got from the beta 1 release was that customers wanted more. Specifically, not only do they want to know when their services are down, but they wanted a way to “peek inside” to see how their various resources are doing before they go down. That’s how Azure Metric Monitoring came to be.

Using Azure Metric Monitoring is just as simple as setting up availability monitoring for it. To begin with, you go to our site at and configure availability monitoring. Spoiler alert – that involves about 2 minutes to fill in a couple of fields and check some boxes – incredibly easy. After you’ve done that, you can go to our Configure Metric Monitoring page at You’ll see another very easy to use interface that looks like this:


What’s great about this approach is that it takes the same very simple and very easy approach we use for availability monitoring. You don’t need to go to the Azure portal and try and create a bunch of policies on each of the different resources you have. Instead, you can come in here and in one place – set the thresholds you want to use for notifications for *all* your resources at once. Just click on the resource type bar – i.e. SQL Database Metrics, Virtual Machines Metrics, etc. – to set the thresholds for those resource types. Click the Update button and you’re done.

After that, we do all the heavy lifting for you. Want to know when the CPU utilization on your SQL Server databases rises above 75%? Want to know when the average response time of the pages on your web sites is more than 10 seconds? How about what kind of network bandwidth you’ve been chewing up with your virtual machines? Or how many queries have been throttled by Search services? The list of possibilities goes on and on here. When any of these thresholds on any of your resources are exceeded, you quickly get notifications about it. Just like all our other notifications, you can get emails, text messages, and/or use our webhook feature so you can plug in your own workflow, on premise notification systems, on premise issue tracking systems, etc.

In addition to that, there are also reports (and more coming) that you can use to get details on what the metric statistics are for all of the resources that we’re watching for you. For example, here’s a set of metrics on all of our Azure web sites:


You can see the most recent 24 hours’ worth of metrics here, but we’ll also have reports that show you what the hourly averages, sums and counts are like over the last week, as well as monthly summaries.

Azure Metric Monitoring is available today as part of our beta 1 service release of AzureServiceMon. It’s free to use while we’re in the beta release, and when you participate you will find other options to extend your free usage once we deliver our RTM release. Check out the Beta 1 Readme for more details on that, as well as to learn about all of the other interesting aspects of this first release.

Azure Metric Monitoring was added based on feedback from our customers using the initial release of AzureServiceMon. Try it out and let us know what you think, and maybe we can get your feature requests added to the service too!

Thanks from Sunny Phoenix,




Azure Availability Monitoring Made Simple at AzureServiceMon

Today we are excited to announce the Beta 1 release of our new Azure availability monitoring service – AzureServiceMon.Com.  We’ve taken all of the great IP and architecture that we’ve used at Office365Mon.Com to build a very powerful, yet incredibly simple to use, service for monitoring the availability of your Microsoft Azure resources.

Getting started is quite simple and for most folks will literally only take a minute or two to get up and running.  You’ll go in and create a new AzureServiceMon subscription, and then tell us to go inventory the list of resources you have with your Azure subscription.  Go grab a cup of coffee, but be quick about it because it normally only takes a minute for us to inventory all of your Azure resources.  Then it’s as simple as checking boxes next to the types of resources that you want us to monitor.  Here’s an example:


After that, well…you’re basically done!  We start our monitoring thing at that point.  You get all of the same great notification options as we have at Office365Mon – emails, text messages, and webhook notifications.  Once we’ve started monitoring, almost immediately you’ll be able to get a snapshot view of what’s going on when you visit your My Info page:


With a quick glance here, I can see I have one or more Traffic Manager outages that are occurring, and if I click on that item it will expand to show me the latest status of each of my Traffic Manager resources so I can see exactly what’s going on.

We also start out with a nice collection of reports for you to use that display summary data for all of the health checks we perform and outages we track.  This includes a great pivot table view of your data, so you can quickly and easily slice and dice your numbers by things like resource Location, resource group, Azure resource type, etc.  Here’s a quick example with a variety of slicers and counts:


There’s a lot here to get started with, but as is always our goal, we’ve tried to make it as simple as possible to get going and start using it.  Everyone can use it for free during the beta release, and if you check out our Beta 1 Readme PDF, you’ll see how you can sign up to get additional free months of monitoring after we complete our beta cycle.

These kinds of releases are also always the best time to give us your feedback about what you like or what you would like to see.  It gives you an opportunity to help shape the service into something that works well for you.

So, for monitoring the availability of your Azure resources, go check out today and click on the big Start Now link to get started.  For monitoring Office 365, go to and use our Start Now link there.

As always, we appreciate your feedback and look forward to building another great monitoring service for you.

From Sunny Phoenix,



Azure Services Monitoring Beta Sign Up

Over the last few years Office365Mon began life as a service to monitor Office 365, and grew from nothing to one of the leading solutions available today.  One of the keys to our growth has been a willingness to listen to customers about what they want, but more importantly – ACT upon what our customers want.  One of the things we’ve heard many times is “we want to monitor our Azure services too”.  Well, as I’ve had the good luck to say many times here, “you ask, we deliver”.

Here at Office365Mon we are in the process of working to bring you a new comprehensive monitoring solution for Microsoft Azure services.  This new service is going to focus primarily on monitoring the availability of key services in Azure.  At launch, we expect to have monitoring available for more than a dozen different kinds of resources, such as SQL Azure databases, web apps, virtual machines, CDNs, event hubs, the Search service, Service Bus, and more.  We also have plans for many additional services, and will be building and deploying them over time.

During the course of building and growing Office365Mon, we built our service entirely on Azure Active Directory and a wide ranging set of Azure services.  Over time we’ve built up quite an appreciation and understanding of these services.  We’re able to take our proven scalable and secure architecture we use for monitoring Office 365 and apply it directly to monitoring these Azure services.  This should give you a high degree of confidence based on the longstanding quality of Office365Mon.

We expect this service – named AzureServiceMon – to beta launch later this summer.  Now is the chance for you to sign up for the beta and see for yourself first hand what it can do.  Getting signed up is quite simple – just go to our new site at and click the Sign Up link.

I hope you’ll take advantage of this opportunity to try it out and give us feedback on what works well, what needs more work, and what additional features YOU would like to see.  Feedback from customers like you is what drives the many features you see in our services today.  If you have any questions, you can send them to us at

From Sunny Phoenix,


ADAL, Native Apps and the “Application Not Found in Directory” Error

It’s been a little while since I’ve written a Native Azure AD app, but as I was doing so today I got poked in the eye again.  I was logging in and using my app no problem with an account from the same tenant where the app was registered in Azure AD.  However when I tried logging in with a user from a different tenant, it failed with the error message “Application with identifier xxx was not found in the directory ‘'”.

I’ve seen that before but it’s been so long that I had to do some hunting around.  I temporarily was sent off course by a suggestion I found (that seemed strangely familiar) to set the oauth2AllowImplicitFlow property to true.  That turned out to not matter at all, but it did at least get me to take a look at the manifest, rather than at the application properties in the Azure portal.

Once in the manifest I found the property that needed to be updated:  availableToOtherTenants.  Set that to true, tried my app again, and my login with a user from a different tenant worked great.  Just thought I would add this to the blog in case you get stuck in the same spot.  These things always seem to take a bit of effort to figure out.


Office365Mon Now Offers Monitoring Out of Regional Data Centers Starting with Germany


Be in the know. Be in control

Office365Mon is now available to be run out of regional Azure data centers around the globe.  In addition to the US data centers, Office365Mon is available today via Germany data centers.


At Office365Mon.Com we’ve heard from customers of our Office 365 monitoring service that had certain data sovereignty restrictions placed upon them.  This means that in some areas, there are government regulations that require data for a company in that region, to be stored in that region.

In addition to that, today Office365Mon issues its health probes out of a US-based data center.  Customers can always (and in fact are encouraged) to augment that with our Distributed Probes and Diagnostics feature, which lets you issue probes from any location where you have users.  However, some folks were hoping to have our cloud-based probes issued from a data center closer to where their users live.

Today we’re happy to announce an option that solves both problems – you can now create Office365Mon subscriptions in regional data centers.  Our first data center is available now, and is located in Germany.  This means not only is your subscription created in Germany, and your health probes are issued out of Germany, but also all of the data we capture is also stored in that same German data center.  That allows you to meet data sovereignty requirements in that region, as well as potentially getting cloud-based probes closer to your users.

One of the first things to call out is that all of the features you get from our US-based service, you will also find in our German-based service.  So no matter where you go, you will find feature parity.  If you have users spread across the globe and want to create Office365Mon subscriptions in different geographies, that’s okay too.  One of the cool things we do is pull together data from all of your subscriptions in every data center when we show you our Power BI reports.  For example, here’s a screenshot the Outages report with data from every subscription in every region for our tenant:


Of course, one of the cool things about Power BI is that you also have a slew of filtering and report building features available to you.  Here’s a screenshot of that same report, only this time it’s filtered to show only data from the Office365Mon subscription that we have in Germany:


The net of this is that if you know Office365Mon today, it will look, work, and act exactly the same no matter what data center your subscription is located.

The next question we expect to get of course is – that’s great, but what if I want Office365Mon in a different geography?  The answer is…that’s great!  Email us and let us know what you are interested in, and we can provide you with an idea of when it can be done.  As long as the different regions have parity in the Azure features that Office365Mon requires, it should be possible to deploy Office365Mon to virtually any regional Azure data center.

There’s only one real difference with using Office365Mon in a regional data center – you have to work with our support team to enable you to get going.  If you contact us at, we will give you all of the details about the on-boarding process, pricing, etc.

We know that this has been in important issue for many of our European friends and customers, so I hope you’ll take a few minutes to take a look at our PDF from our US site or our German site.  Of course, you can also visit our US site directly at, or our new German site at

Thanks as always for your great suggestions and ideas!
From Sunny Phoenix,


Now You Can Monitor OneDrive and Power BI with Office365Mon

Today we’ve released two new features that customers have been asking us about – monitoring for OneDrive for Business and Power BI.  These are just the latest set of services in an ever increasing stable of monitored features and services from Office365Mon.  Let’s take a quick look at each.

OneDrive for Business

Office365Mon has actually been able to monitor OneDrive for Business since our first release over two years ago.  However, many customers weren’t really aware of that and didn’t realize that when you configure monitoring for SharePoint Online, you could just tell it to go monitor a OneDrive site.  What we’ve done is to break OneDrive out as a separate monitored item on your Office365Mon subscription.  This gets you a couple of things – first, now you can monitor both a SharePoint Online site and a OneDrive site with the same subscription.  Second, it also allows us to give you a more granular breakdown of both performance and availability with your SharePoint Online tenant.  For example, here’s a report with the average performance across all Office365Mon customers for the primary Office 365 Services:


As you can see with the yellow bar, now you can see what performance is like just on OneDrive sites vs. SharePoint Online sites from all of our customers.  Of course, you’ll also be able to see what performance is like just for your tenant in OneDrive.  We think breaking OneDrive out in this way will give you an even deeper view into the health and performance of your tenant, which is a great thing.

Power BI in Office 365

The second feature we added is brand new, and something that we’ve heard customers ask us about for a while now.  Power BI is increasingly becoming a critical part of the toolset that customers are using, so of course it’s important to know how well it’s performing and when it goes down.  Our new monitoring for Power BI does all of that, just as you’ve come to expect from Office365Mon.  The configuration of Power BI monitoring is drop dead simple, which is also something you’ve come to expect from us.  You literally click a single button – that’s it – as shown in this screenshot below:


Once you’ve enabled it, health probes begin a minute or two later; can’t get much easier than that!  Once we start collecting the data, details on performance and availability of Power BI show up in all of the same reports that you’ve already been using.  For example, here’s a screenshot of the recent health probes report, showing you the performance of your monitored resources:


As you can see, you get the performance of your individual resources that are being monitored – including both Power BI and OneDrive – and that is overlaid on top of a bar chart with the overall numbers from all Office365Mon customers with the average performance for Exchange Online, SharePoint Online, OneDrive and Power BI.  Our goal is always to show you as much relevant data as possible and then give you the opportunity to drill down and filter as best suits your requirements.  Also, like all of our reports, you can add this to your own corporate intranet for anyone you want to be able to see, by using our Dashboard Reports feature.  Meanwhile, should Power BI go down, you can also take comfort in the fact that you’ll get all of the same notifications from us as you do today for all of your other monitored services.  Power BI is just another one of “the team” now, and is monitored just like all of the other features and services we’re keeping an eye on for you.


Try it Out

Both the OneDrive and Power BI monitoring features are available for you to try out now.  All existing Office365Mon customers as well as all new customers will have access to these features for 90 days.  New customers can go create an Office365Mon subscription at  No payment information is required up front, and if you choose not to use it there’s nothing you need to do – after 90 days we just stop monitoring stuff for you.

For all Office365Mon paid subscriptions, we will continue to monitor OneDrive for you.  Power BI monitoring requires the Enterprise Platinum license.  If you have that, monitoring Power BI will continue for you; if you don’t have that license, you can upgrade to it at any time by going to our Payments page at


Thanks Again

As always, thanks again for the many terrific suggestions you all have provided.  We’re always looking for ways in which we can do a better job meeting your needs, and the best way to do that is for you to let us know what’s important to you.  Office365Mon really has a wide range of monitoring features now, so I hope if you haven’t tried it yet, or maybe if it’s been a while since you’ve looked at it, you’ll come by and take it out for a spin for 90 days.  We think you’ll find that it’s well worth the 2 minutes of your time to get things set up and going.


From Sunny Phoenix,


Monitoring Exchange Online Errors You Might Not Otherwise Notice with Office365Mon

We introduced monitoring for the email transport for Office 365 customers back in February of this year after strong demand from our customers (  We had provided monitoring of the email service itself since Day 1, but if your mailbox is up but the messages you send don’t go out, or the message people send you don’t make it in, then email is of pretty limited value.  As we moved the email transport monitoring service out into production and began gathering more and more data, we started finding a few common errors that many tenants were experiencing, but which are innocuous enough you might not even know that they are happening.

We decided to create some new reports around the email transport monitoring feature to help customers understand better when these situations occur.  Sometimes they point out problems that customers can resolve themselves, and other times it’s just good to understand better when and where the hiccups are in your email service.  In a nutshell, as we capture more data around errors in the transport, we are bubbling up the common errors into these new reports so you can see for yourself when they happen and how frequently they happen.

If you go into the Advanced Reports gallery on our site at, there are new “Recent Email Transport Errors” and “Monthly Email Transport Errors” reports.  The Recent Email Transport Errors report is a simple tabular list of the 100 most recent instances of these common errors described above.  Here’s a sample report:


As you can see, we indicate whether the issue was with an inbound or outbound email, when it happened (most recent first), and what the problem was.  This report has already paid off big for one of our customers, because with the information in it they were able to determine that they had an old MX record in DNS, and that MX record pointed to a server that was no longer available.  This showed up in our reports every time that server was selected for us to send mail to it, and as a result they were able to clean that up in their environment.  Some of the other common problems we see are things like Outlook API service is temporarily unavailable, the anti-spam features have incorrectly marked an outbound message as spam (and as a result it gets stuck in the Drafts folder)…happens most frequently with email accounts by the way, and requests to the service are unauthorized (which could be your access token has expired or Azure Active Directory is temporarily unavailable).  Some things you may be able to fix yourself; other things it’s just good information to have so you are aware of how well your transport features are performing.

The Monthly Email Transport Errors report helps you stay on top of this by presenting a bar chart with a count of each type of error, so you can see how frequently each type of error is occurring in your tenant each month.  Here’s an example of that:


At Office365Mon our position is you can never have too much good information.  Based on the early results of this reporting, we’re already seeing good outcomes and actionable data for our customers.  If you aren’t set up for Office 365 monitoring yet, please visit our web site at to get started.  Once you’ve configured basic monitoring, you can turn on email transport monitoring at to get these reports yourself.  We’ll be continuing to mine through the data and expand out the collection of common errors as we see them.

As always, please feel free to send us your feedback at and thank you for all of the great ideas you’ve sent us already.

From Sunny Phoenix,