When you register a new application in Azure AD, especially those that will be used to login users or gather additional permissions, the branding section, specifically the Logo of the App is often overlooked.
But what is the logo, where does it even show up?
First, and most importantly, it is displayed when the users need to consent to using your application when they first log-in:
There are many ways to insert data in Cosmos DB and many use cases when you want to do that. In this article we’ll dive in the use case of bulk-updating a Cosmos DB collection based on a feed of data or some kind of recurrent data ingestion process into Cosmos DB. The
Sync jobs, daily jobs that need to populate data into a Cosmos DB collection…
I’ll evaluate the solutions based on a few factors: cost, speed, development time, complexity of solution.
What an amazing update about performance improvements in the upcoming .NET 5 by Stephen Toub!
A 1h+ read with so many amazing tidbits of information. Thank you Stephen for posting.
If you can, the article it’s definitely worth the time reading, but if not, here’s the TL;DR; version where I will extract some of the performance improvement for the things you probably are using today in your application and that will get these performance boosts with nothing else than updating your application to the new runtime.
I recently had to fix a bug in an older codebase that did not follow the best practices when handling date times. In short, every Date Time in the application was expecting / using an EST date time since the project was traditionally deployed on-prem.
With the move to Azure, dates no longer defaulted to EST and since it wasn’t feasible to convert the entire codebase to properly use UTC, I had to update my code to use EST.
One of the nicest things about Logic Apps is how seamless and fast their execution goes and how little you have to worry about managing concurrency and execution times,
until you do…
Day 2 of BUILD brought a lot of very cool sessions and more updates. Below are some notes from some of the sessions that I was able to attend do that I wanted to make sure get the attention they deserve
So, Day 1 of BUILD 2020 is behind us now, here are a few of the most exciting announcements (for me) and links to more details
I think API Management needs no introduction these days and it’s a no brainer to use it when developing APIs that back up any kind of customer facing apps thanks to its slew of features such as protection via subscriptions, monitoring, caching, or even some of the less obvious ones such as offering you the ability to seamlessly swap out your undelaying API without customer impact.
However in this article I want to talk about another feature that I just learned about and used successfully for the first time, the managed identity integration.
I’ve always enjoyed analyzing Azure Cost usage and patterns and have successfully helped 2 clients so far get a deeper understanding of their azure cost by exposing the data in a nice PowerBI dashboard.
As everyone who’s played with this before know, the key to good cost control and insights is good tagging.
So once I had the tagging strategy established we went ahead and tagged all the Resource Groups in the subscription(s). Once that was done it was time to push those tags down to the resources.
To do that, I decided the quickest (?) way to get there was to write a nice little power shell script to apply tags set at a Resource Group level, to its child resources.
If you’re looking at a quick, serverless and no-code solution to load data into your Cosmos DB database, you should look no further than Data Factory. With it’s multitude of connectors for sourcing data and its built in sink connector for CosmosDB, you can quickly create a data pipeline to ingest, refresh or keep your Cosmos Database in sync.
Read the rest of the article for a quick step-by-step guide on setting this up. One caveat, this only works for a SQL CosmosDB account for now.