Azure Policy is a service in Azure that you use to create, assign, and manage policies that enforce rules over your resources to ensure compliance against corporate standards and service level agreements (SLAs). An initiative is a collection of policies grouped together. An Initiative simplifies managing and assigning policies by grouping them as one single item. Azure Policy is comprised of three components – Enforcement and Compliance, Application at Scale, and Remediation. You will have the ability to turn on built-in policies or build custom policies for all resource types, evaluate and enforce policies real-time, assess compliance and a newly added feature, VM In-Guest Policy that allows you to audit settings inside a machine. Azure Policy also allows you to apply policies to a Management Group with organization-wide control, apply multiple policies and aggregate policy states with policy initiative AND…
I work on many APIs with clients, and a trend I have noticed is that very few of the tools available are being used. What do I mean by this? It means that all the requests are GETs or POSTs, or all the responses are 200s, 400s, or 500s. If that means nothing to you, then I’m not really surprised, and I will clarify as this carries on.
Let’s start with API request “verbs.” These are the GETs and POSTs I mentioned above. Believe it or not, there are more than just those two. Basically, what I have discovered is a mentality that if the request has/needs body content, it’s a POST, else GET. Please, please, if you follow this pattern, forget it and read on, but there is a chance all your requests will still be GETs or POSTs.
Alright, let’s discuss…
If your organization has multiple Azure subscriptions, you may need a way to efficiently manage access, policies, and compliance for those subscriptions. This can be accomplished through Management Groups. Through Management Groups, you can: (1) group subscriptions allowing for new organizational models and single assignment of controls that apply to all subscriptions. (2) create a flexible hierarchy that can be updated quickly and can easily scale up or down depending on the needs of the organization, and (3) use Azure Resource Manager to integrate with other Azure services like Policy, Cost Management, Blue Prints, and Security Center.
In this simple example, using Management Groups, we have created an organizational hierarchy. Starting at the corporate level, we have created two management groups – one for the Marketing team and one for the IT team. Within the IT group, we have established two…
A couple of weeks ago, Tallan attended its first ALM LegalWeek conference in New York City. With over 4,000 attorneys, c-suite executives, marketing and business development staff, exhibitors, and vendors registered, our team was looking forward to networking and the educational panels we had the opportunity to attend.
The event was divided into three separate ‘conferences,’ Legal CIO, Legal Tech, and Legal Business Strategy. We divided and conquered, and after day 1, one thing became clear: LegalTech has become mainstream. Firms are looking for out-of-the-box products and platforms to enhance processes, time-keep for ease of billing, foster eDiscovery, and generally optimize operations. There are vendors for nearly every ‘LegalTech’ you could imagine or need.
For the most part, they are internal. Save time by digitizing records, but if a firm cannot bill that time saved (not that attorneys perform administrative tasks anyway), then how…
As a UX designer, I was tasked with a QA assignment that required me to change hats. QA needs direction, and it is essential that UX delivers designs that have a story in the form of journey maps and sitemaps so QA can create test cases with useful sample data for effective interactive testing. It is important to have visual workflows and explicit instructions that can be easily followed by developers, which in turn provides QA with a clear direction in testing efforts.
Walking through test cases as a QA with a UX background allowed me to see what most developers may not recognize including simple usability issues that may not have been thought of:
Visibility of system status
Match between system and the real world
User control and freedom
Consistency and standards
Recognition rather than recall
Flexibility and efficiency of use
Aesthetic and minimalist design
I often receive requests from colleagues needing to solve particularly thorny problems from within a SQL database. This article is intended for those who might find themselves needing to parse a delimited string inside a SQL database, those who find themselves in a position to provide solutions to this particular issue and those liking SQL challenges.
Recently a colleague posed a problem where the value in one column was a list of user property metadata. Each user property was a list of the information required to extract values from a second column in the same table, a list within a list with a common delimiter throughout. A key-value pairs table is a suitable design for this application; the designer chose a different path. The data and the metadata about that data were denormalized into separate columns. Our goal is to determine a solution…
The speed at which companies are moving to the cloud continues to accelerate. When the cloud-first came to be, the question was, why? Why should we relinquish control of our infrastructure? Once there was a reasonable answer to why, it became a matter of if, if we are going to move to the cloud. Now it’s a matter of when. And now that we’re there, the question has become, how do we organize everything and maintain control? In short, Governance. Governance enables you to; (i) establish control by implementing policies with real-time enforcement, compliance assessment, and remediation, (ii) deploy and update cloud environments in a repeatable manner using composable artifacts, (iii) query, explore, and analyze cloud resources at scale, (iv) define an organizational hierarchy, and (v) monitor cloud spend and optimize resources. Next week, we will begin a four-part mini-series on…
What is a Directive?
Now we know how to make custom validators, which can significantly enhance user experience with more specific error messages that can pop up before submission. However, sometimes the answer that the user inputted is not quite what you are expecting, but not necessarily wrong. In these cases, you need to decide if it is better to leave the result as is, display a (hopefully descriptive) error message, or adjust the response. In this blog post, we’re going to focus on the third option, utilizing Angular directives to change the user response slightly as a gentle alert to the user that we will be saving their response in a different format than what they had originally inputted.
What exactly is a directive? Attribute directives, which is what we will be working with, are responsible for changing the appearance or…
What are Angular Forms?
Angular has become a powerful tool in application development over the years. Companies in every field utilize this framework to create powerful websites that provide a clear and fast user experience. In many cases, there is a need to collect information from the user, for everything from gauging user experience to collecting vital documents and information when a claim is being filed. Angular has two different types of forms that are optimized for effective data collection from the user. Template-driven forms are asynchronous in nature and known for having most of their logic driven by the template. Reactive driven forms are known for being mostly synchronous and having logic that primarily resides in the component. In this blog, we will be tackling reactive forms, and more specifically, how to make your life easier with more readable validators.
What is Azure Service Bus?
Azure Service Bus is an integration message broker used as a reliable platform for asynchronous data transfer between different applications and services. Data is transferred using messages which can contain JSON, XML, or simply text. These messages are either transferred over queues or topics. In short, queues are used for point-to-point communication between one sender and one receiver, and topics are used in publisher/subscriber scenarios, with one sender and multiple, subscribing receivers. This Microsoft document provides a more detailed explanation of the Service Bus, Queues, and Topics, as well as some advanced features to solve more complex messaging problems.
This article will provide an example implementation of an Azure Service Bus connecting two .NET Applications.
Implementing Azure Service Bus
Setting up a Service Bus through the Azure portal is a very simple process,…