Why Not? Automating Coffee Break Notifications with Azure Logic Apps

Let’s face it, folks: productivity peaks when caffeine flows. But how often do you lose track of time, only to realize you’ve been glued to your screen without your essential coffee break? Enter Azure Logic Apps, your caffeine accountability buddy.

Yes, we’re automating coffee break reminders. Is it silly? Absolutely. Is it also a fantastic way to show off your Logic Apps skills? You betcha. Let’s build it—with full code, because you deserve it.

The Plan

Here’s what we’re building:

  1. Trigger: The Logic App runs every workday at a specific time.
  2. Check Your Calendar: Ensure you’re not in a meeting during coffee time.
  3. Send a Reminder: Notify yourself to take a break and caffeinate responsibly.

Create the Logic App

First, create a Logic App in the Azure Portal (Consumption Plan) and name it something clever like CoffeeBreakBuddy. We are building a caffeine ally here afterall.


Full Code: Coffee Break Reminder Logic App

Here’s the complete code for your new caffeine buddy in JSON. Save it as a .json file and import it into the Azure Logic Apps designer

{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"actions": {
"Check_Calendar": {
"inputs": {
"host": {
"connection": {
"name": "@parameters('$connections')['office365']['connectionId']"
}
},
"method": "get",
"path": "/v2/calendars/me/events",
"queries": {
"$filter": "start/dateTime ge '@{utcNow()}' and start/dateTime lt '@{addMinutes(utcNow(),30)}'"
}
},
"runAfter": {
"Recurrence": [
"Succeeded"
]
},
"type": "ApiConnection"
},
"Condition": {
"actions": {
"Send_Reminder": {
"inputs": {
"body": {
"Content": "It's coffee o'clock! Take a break and enjoy your brew. ☕"
},
"host": {
"connection": {
"name": "@parameters('$connections')['office365']['connectionId']"
}
},
"method": "post",
"path": "/v2/emails",
"headers": {
"Subject": "Coffee Break Reminder"
}
},
"type": "ApiConnection"
}
},
"expression": {
"and": [
{
"equals": [
"@empty(body('Check_Calendar')?['value'])",
true
]
}
]
},
"runAfter": {
"Check_Calendar": [
"Succeeded"
]
},
"type": "If"
}
},
"triggers": {
"Recurrence": {
"recurrence": {
"frequency": "Day",
"interval": 1,
"schedule": {
"hours": [
10
],
"minutes": [
0
]
}
},
"type": "Recurrence"
}
}
},
"parameters": {
"$connections": {
"defaultValue": {},
"type": "Object"
}
}
}

How It Works

Trigger: Recurrence

  • Runs every day at 10:00 AM. Adjust the time in the schedule property under Recurrence.

Check Your Calendar

  • Uses the Office 365 Outlook connector to check for events in the next 30 minutes.

Condition: Is It Coffee Time?

  • If your calendar is empty during the coffee break window, it sends a reminder.
  • If busy, skips the reminder because productivity comes first (sometimes).

Send Reminder

  • Sends an email through the Office 365 connector. You can change this to a Teams message or even a text with Twilio.

How to Deploy

  1. Import the JSON:
    • In the Logic Apps designer, click Import Logic App and upload the JSON file.
  2. Set Up Connections:
    • Add an Office 365 Outlook connection for email and calendar integration.
  3. Save and Run:
    • Save your Logic App and test it by running it manually or waiting for the next scheduled run.

Bonus Ideas

  • Add weather data to suggest iced or hot coffee.
  • Hook up Spotify to start a “Coffee Break” playlist.
  • Track your breaks in Azure Table Storage to analyze your caffeine habits.

Now go forth and caffeinate like a boss. And remember, this isn’t just about coffee—it’s about showing the world that no problem is too small to automate. Cheers!

Azure Monitor Agent: Time to Ditch the Old and Embrace the New

Hey there fellow geeks! If you’ve been snoozing on Azure updates, it’s time to wake up and smell the deprecation notices. As of August 31, 2024, the trusty old Log Analytics Agent (also known as MMA) is heading to the retirement home. That’s right—Microsoft is pulling the plug.

But don’t panic! The Azure Monitor Agent (AMA) is here to save the day, offering a sleeker, more efficient way to keep tabs on your virtual machines and servers. Let’s dive into why you should make the switch and how to do it without breaking a sweat.


Why Should You Care?

The Log Analytics Agent has been a faithful companion, but it’s showing its age. The Azure Monitor Agent brings a host of improvements:

  • Centralized Configuration: Manage multiple VMs with ease from a single pane of glass.
  • Enhanced Performance: Less resource hogging, more monitoring efficiency.
  • Better Security: Tighter integration with Azure’s security features to keep those pesky threats at bay.
  • Support for More Data Sources: Broader data collection to give you a more comprehensive view of your environment.

The Clock Is Ticking: Migration Steps

Alright, let’s get down to business. Here’s how to bid farewell to MMA and roll out AMA like a pro:

  1. Assess Your Current Setup: Identify all VMs and servers still running the Log Analytics Agent.
  2. Plan the Migration: Determine the order of migration, considering critical systems first.
  3. Install the Azure Monitor Agent: Use Azure Policy or deployment scripts to install AMA across your resources.
  4. Configure Data Collection: Set up data collection rules to specify what data to gather and where to send it.
  5. Test the Setup: Ensure AMA is collecting data as expected before decommissioning MMA.
  6. Decommission the Old Agent: Once confirmed, uninstall the Log Analytics Agent from your systems.

For a detailed walkthrough, check out Microsoft’s official guide: Migrate to Azure Monitor Agent.


Don’t Be That Person

Procrastination is the enemy here. Delaying the migration could leave your systems unsupported and vulnerable. Plus, who wants to be scrambling at the last minute? Get ahead of the curve and make the switch to AMA today.

Remember, change is inevitable—except from a vending machine. Embrace the new, retire the old, and keep your monitoring game strong. Learn more about the Azure Monitor Agent.

Happy migrating!

Azure Communication Services: March 2024 Updates You Need to Know

Alright, folks, buckle up because Azure Communication Services (ACS) just dropped a batch of updates that’ll make your dev life a little smoother and your apps a lot smarter. Whether you’re building chat, voice, or video features, ACS has some shiny new tools to simplify your workflows and impress your users.

Let’s break it down.


Limited Access User Tokens: Now Generally Available

Ever wanted to give your users just enough access to get the job done without opening the floodgates? Meet Limited Access User Tokens. These beauties let you control what users can and can’t do—like joining a call but not starting one.

Think of it like a VIP pass that only gets you into the lounge, not backstage. Perfect for scenarios where security and controlled participation are a must. And yes, it’s available right now for you to play with.


“Try Phone Calling” (Public Preview)

Imagine this: you’re setting up telephony in your app, but you’re not 100% sure the setup actually works. Enter “Try Phone Calling”, now in public preview. This feature lets you make test calls directly from the Azure portal. No code. No app. Just you, a test call, and sweet, sweet confirmation that everything’s running smoothly.

This works with both PSTN (Public Switched Telephone Network) and direct routing setups. It’s like a “Hello, World” for phone calling.


UI Native Library Gets a Boost

The Native UI Library just got a couple of upgrades that’ll make your users love you even more (or at least blame you less when something goes wrong):

  1. User Facing Diagnostics (UFD): Think of this as your app whispering helpful tips to users. Muted mic? Bad network? UFD lets users know in real-time so they can fix issues themselves. No more “I can’t hear you” panic in the middle of a call. It’s available now, so start showing off your polished UX skills.
  2. iOS CallKit Integration: For all the Apple fans out there, ACS now integrates with iOS CallKit (in public preview). Your calls will feel native, with built-in notifications, call history, and even call hold. It’s like giving your app a little iOS magic wand.

PSTN Direct Offers Expanded

PSTN Direct Offers just leveled up with availability in 42 countries. That’s 400+ new cross-country offers, making it easier to integrate phone calling into your app no matter where your users are.

If you’ve been dreaming of adding PSTN calling for global users, this update is basically your green light.


Why These Updates Matter

Azure Communication Services just made it a lot easier to build reliable, secure, and scalable communication features into your apps. From tighter access controls to test calls and diagnostics, these tools are all about making your life easier and your apps better.

You can dive into the nitty-gritty here: Azure Communication Services Updates. Or just fire up the portal and start playing around. You’ll thank yourself later.

Now, go forth and communicate like the app-building rockstar you are.

PowerShell’s Pseudo-Terminal Support: A Hidden Gem for the Command Line

Ah, PowerShell—the Swiss Army knife of scripting languages. Just when you think you’ve explored all its tools, it unveils a new feature that makes you wonder how you ever lived without it. Today, we’re diving into one such feature that might have flown under your radar: pseudo-terminal support. If you’re moderately skilled in PowerShell, prepare to have your command-line experience elevated.

What on Earth Is Pseudo-Terminal Support?

In the realm of command-line interfaces, a pseudo-terminal (PTY) acts as a mediator between a user and the system, emulating a physical terminal. This allows for more sophisticated interactions with native commands, enhancing how input and output are handled within PowerShell.

Why Should You Care?

Traditionally, PowerShell has had limitations in capturing and managing the output of native commands. This often led to challenges in scripting and automation, especially when dealing with complex command-line tools. With pseudo-terminal support, these limitations are addressed, offering:

  • Improved Output Handling
  • Enhanced Interactivity
  • Streamlined Automation

How Does It Work?

Pseudo-terminal support allows PowerShell to create a virtual terminal session for native commands. This means that when you execute a command, PowerShell can interact with it as if it were running in a standalone terminal, capturing all output and managing input more effectively.

Before Pseudo-Terminal Support

Imagine trying to run a command that requires interactive input, like ssh or cmd.exe /c pause. Before PTY support, PowerShell struggled to manage interactive commands cleanly. Here’s an example:

# Before PTY Support
Start-Process -FilePath "cmd.exe" -ArgumentList "/c pause" -NoNewWindow -Wait

In this case, interactive prompts might not behave as expected, or the output could be garbled, making automation difficult.

After Pseudo-Terminal Support

With PTY support enabled, PowerShell now handles such scenarios seamlessly, making it much more robust for interactive use cases. Here’s the improved approach:

# After PTY Support (Requires PowerShell 7.5+ and PTY enabled)
$session = New-Object System.Management.Automation.Host.PseudoTerminalSession
$session.StartProcess("cmd.exe", "/c pause")
$session.WaitForExit()

Now, PowerShell interacts directly with the pseudo-terminal, meaning smooth execution and proper handling of inputs and outputs.


Enabling Pseudo-Terminal Support

As of PowerShell 7.5, pseudo-terminal support is available as an experimental feature. To enable it:

  1. Update PowerShell: Ensure you’re running PowerShell 7.5 or later.
  2. Enable the Feature: Use the following command to turn on PTY support:
Enable-ExperimentalFeature -Name PseudoTerminalSupport

3. Restart PowerShell: Close and reopen your PowerShell session to apply the changes.

By leveraging pseudo-terminal support, PowerShell scripts become more capable of managing interactive commands and complex workflows, unlocking new possibilities for automation. Experiment with it and see how it fits into your toolkit!

PowerShell 7.5.0 Preview 2 Changes

Preview 2 has dropped! Let’s look at some of the major things that are coming in this preview.

First – let’s look at the breaking changes:

Breaking Changes

  • Adjustments have been made to the -OlderThan and -NewerThan parameters for Test-Path, addressing issues when used with PathType and a date range​
  • The default CatalogVersion for New-FileCatalog has been changed to 2​​
  • Restrictions have been added to block help from network locations in restricted remoting sessions​

And now to the improvements:

Tab Completion Improvements

  • Efforts led by contributors like @ArmaanMcleod have refined tab completion, including preventing fallback to file completion when tab completing type names and adding argument completers for various cmdlets like Set-StrictMode, Get-Verb, Start-Process, and more​

Web Cmdlets Improvements

  • Fixes have been made to Invoke-WebRequest to ensure accurate size reporting when the -Resume parameter is specified​
  • Web Cmdlets have been adjusted to allow WinForm applications to work correctly​

Other Cmdlet Improvements

  • A range of cmdlet improvements and fixes, including for Test-Connection, Get-Service, and adding new parameters to New-Guid. For instance, New-Guid now supports -Empty and -InputObject parameters​

Engine Improvements

  • Enhancements in the engine include telemetry for module imports, adjustments to module load telemetry, and fixes for regressions introduced by the WDAC logging feature​

Experimental Features

  • Introduction of tilde expansion for Windows native executables, demonstrating PowerShell’s ongoing evolution and adaptation​

​.

PowerShell, GitHub, and the GH Cli

Here’s another quick one – using the GitHub CLI to copy a repository from GitHub, bring it down to your local machine, and then copy it to a remote server. Great for quickly setting up a new automation server or re-baseline an existing box.

Before running the script, ensure:

  • You have permissions to access the remote server and write to the target directory.
  • PowerShell Remoting is enabled on the remote server if you’re using a PowerShell session for the transfer.
  • The GitHub CLI is installed and configured on your machine.

Here’s the script!

# Define variables
$repoUrl = "https://github.com/username/repository" # Replace with your GitHub repository URL
$tempDir = Join-Path -Path $env:TEMP -ChildPath "github_repo_temp"
$remoteServer = "\\remote-server\share" # Replace with your remote server share path
$remotePath = "path\to\destination\folder" # Replace with your remote destination path, relative to the share

# Ensure the temp directory does not already exist
if (Test-Path -Path $tempDir) {
    Remove-Item -Path $tempDir -Recurse
}

# Clone the repository to the temporary directory
gh repo clone $repoUrl $tempDir

# Assuming the remote server is accessible via a network share
$fullRemotePath = Join-Path -Path $remoteServer -ChildPath $remotePath

# Ensure the remote directory exists
if (-not (Test-Path -Path $fullRemotePath)) {
    New-Item -Path $fullRemotePath -ItemType Directory
}

# Copy the contents to the remote server
Copy-Item -Path "$tempDir\*" -Destination $fullRemotePath -Recurse

# Clean up the temporary directory
Remove-Item -Path $tempDir -Recurse

Write-Host "Repository contents have been copied to the remote server."

And that’s it! Consider putting it in a scheduler to always ensure that your remote automation servers are up to date and using your latest code.

Enjoy!

Running PowerShell from a Logic App

Hola! Today let’s look at a simple way to get PowerShell scripts to run from a Logic App. It will involve a single extra tool, but this really adds versatility to an already versatile tool.

Start by creating a PowerShell script for your specific task. This script will be uploaded to an Azure Automation Runbook. For instance, if you aim to manage VMs, ensure the script includes Azure RM or Az module commands to start, stop, or monitor VM states. Here is an example:

# Sample PowerShell Script to Start a Specific Azure VM
Param(
    [string]$vmName,
    [string]$resourceGroupName
)

Connect-AzAccount -Identity
Start-AzVM -Name $vmName -ResourceGroupName $resourceGroupName

Obviously this is a short script that we can do with just Logic Apps (and not involve pwsh at all), but you get the point.

Now – Upload and publish your PowerShell script in an Azure Automation Runbook.

  1. In your Azure Automation Account, create a new Runbook.
  2. Choose “PowerShell” as the Runbook type.
  3. Import your script and publish the Runbook.

Go ahead test the runbook if you want.

Next – create a Logic App to trigger the Runbook. You might use a schedule, an HTTP request, or another event in Azure as a trigger.

  1. In the Logic App Designer, add a new step and search for the “Azure Automation” connector.
  2. Select “Create job” action.
  3. Fill in the necessary details: Automation Account, Runbook Name, and parameters (if your script requires them). In our example we might dynamically pass the VM name, or maybe look for only VMs that are off and loop through them.

For more complex scenarios, you might need to integrate with other Azure services before or after executing your PowerShell script:

  • Azure Functions: For custom logic that cannot be implemented directly in PowerShell or needs a specific runtime environment.
  • Azure Event Grid: To trigger your Logic App based on events from various Azure services.
  • Azure Monitor: To analyze logs and metrics from your Logic App and Automation Runbooks, enabling proactive management and optimization of your automated tasks.

And there you go! Go put PowerShell everywhere!

Quick Code – Install AMA and Assign a DCR with PowerShell

Happy Holidays! Here’s a quick post to share some code that will inventory Azure VMs, install the AMA if necessary, and then assign a DCR to the VM.

# Ensure you're logged in to Azure
Connect-AzAccount

# Define the Data Collection Rule (DCR) resource ID
$dcrResourceId = "<Your-DCR-Resource-ID>"

# Get all VMs in the subscription
$vms = Get-AzVM

# Use ForEach-Object with -Parallel to process VMs concurrently
$vms | ForEach-Object -Parallel {
    $vm = $_
    $osType = $vm.StorageProfile.OsDisk.OsType
    $extensionName = if ($osType -eq "Windows") { "AzureMonitorWindowsAgent" } else { "AzureMonitorLinuxAgent" }
    $extensionPublisher = "Microsoft.Azure.Monitor"
    $vmResourceId = "/subscriptions/$using:vm.SubscriptionId/resourceGroups/$using:vm.ResourceGroupName/providers/Microsoft.Compute/virtualMachines/$using:vm.Name"

    try {
        # Check if the Azure Monitor Agent extension is installed
        $amaExtension = Get-AzVMExtension -ResourceGroupName $using:vm.ResourceGroupName -VMName $using:vm.Name -Name $extensionName -ErrorAction SilentlyContinue

        if (-not $amaExtension) {
            try {
                # Install the Azure Monitor Agent extension
                Set-AzVMExtension -ResourceGroupName $using:vm.ResourceGroupName -VMName $using:vm.Name -Name $extensionName -Publisher $extensionPublisher -ExtensionType $extensionName -TypeHandlerVersion "1.0" -Location $using:vm.Location
                Write-Host "Installed Azure Monitor Agent on $($using:vm.Name)"
            } catch {
                Write-Host "Failed to install Azure Monitor Agent on $($using:vm.Name): $_"
            }
        } else {
            Write-Host "Azure Monitor Agent is already installed on $($using:vm.Name)"
        }
    } catch {
        Write-Host "Error checking Azure Monitor Agent on $($using:vm.Name): $_"
    }

    try {
        # Assign the DCR to the VM
        $settings = @{ "dataCollectionRuleResourceIds" = @($using:dcrResourceId) }
        Set-AzVMExtension -ResourceGroupName $using:vm.ResourceGroupName -VMName $using:vm.Name -Name "AzureMonitorVmExtension" -Publisher $extensionPublisher -ExtensionType $extensionName -Settings $settings -Location $using:vm.Location
        Write-Host "Assigned DCR to $($using:vm.Name)"
    } catch {
        Write-Host "Failed to assign DCR to $($using:vm.Name): $_"
    }
} -ThrottleLimit 5 # Adjust the ThrottleLimit as necessary

Setting up Azure OpenAI with PowerShell

If haven’t been living under a rock, you know that Azure OpenAI is a powerful tool that brings the cutting-edge capabilities of OpenAI’s models to the cloud, offering scalability, reliability, and integration with Azure’s vast ecosystem.

Because I am who I am we will use PowerShell to setup our Azure OpenAI instance. Whether you’re automating deployment or integrating Azure OpenAI into your existing infrastructure, PowerShell scripts can simplify the process. Let’s get started with a step-by-step guide to setting up your Azure OpenAI instance using PowerShell.

Prerequisites

Before we dive into the commands, ensure you have the following:

  • An Azure subscription. If you don’t have one, you can create a free account.
  • PowerShell installed on your system. If you’re on Windows, you’re probably already set. For Mac and Linux users, check out PowerShell Core.
  • The Azure PowerShell module installed. You can install it by running Install-Module -Name Az -AllowClobber -Scope CurrentUser in your PowerShell terminal.

Step 1: Log in to Azure

First things first, let’s log into Azure. Open your PowerShell terminal and run:

Connect-AzAccount

This command opens a login window where you can enter your Azure credentials. Once authenticated, you’re ready to proceed.

Step 2: Create a Resource Group

Azure OpenAI instances need to reside in a resource group, a container that holds related resources for an Azure solution. To create a new resource group, use:

New-AzResourceGroup -Name 'MyResourceGroup' -Location 'EastUS'

Replace 'MyResourceGroup' with your desired resource group name and 'EastUS' with your preferred location.

Step 3: Register the OpenAI Resource Provider

Before deploying Azure OpenAI, ensure your subscription is registered to use the OpenAI resource provider. Register it with:

powershell

Register-AzResourceProvider -ProviderNamespace 'Microsoft.OpenAI'

This command might take a few minutes. To check the status, you can run Get-AzResourceProvider -ProviderNamespace 'Microsoft.OpenAI'.

Step 4: Create an Azure OpenAI Instance

Now, the exciting part—creating your Azure OpenAI instance. Use the following command:

powershell

New-AzResource -ResourceGroupName 'MyResourceGroup' -ResourceType 'Microsoft.OpenAI/workspaces' -Name 'MyOpenAIInstance' -Location 'EastUS' -PropertyObject @{ sku = 'S0'; properties = @{ description = 'My Azure OpenAI instance for cool AI projects'; } }

Make sure to replace 'MyResourceGroup', 'MyOpenAIInstance', and 'EastUS' with your resource group name, desired OpenAI instance name, and location, respectively.

Step 5: Confirm Your Azure OpenAI Instance

To ensure everything went smoothly, you can list all OpenAI instances in your resource group:

powershell

Get-AzResource -ResourceGroupName 'MyResourceGroup' -ResourceType 'Microsoft.OpenAI/workspaces'

This command returns details about the OpenAI instances in your specified resource group, confirming the successful creation of your instance. Enjoy your brand new OpenAI instance!

Quick Dive: Integrating Logic Apps with Azure OpenAI

Let’s cut to the chase: Integrating Azure Logic Apps with Azure OpenAI unlocks a plethora of possibilities, from automating content creation to enhancing data analysis. Below is a step-by-step guide to melding these powerful tools.

Step 1: Set Up Azure OpenAI

First, you need an Azure OpenAI service instance. Go to the Azure Portal, search for Azure OpenAI Service, and create a new instance. Once deployed, grab your API key and endpoint URL from the resource management section.

Step 2: Create Your Logic App

Navigate back to the Azure Portal and create a new Logic App:

  • Choose your subscription and resource group.
  • Pick a region close to you for lower latency.
  • Name your Logic App.
  • Click “Review + create” and then “Create” after validation passes.

Step 3: Design Your Logic App Workflow

Once your Logic App is ready, it’s time to design the workflow:

  • Open your Logic App in the Azure Portal and go to the Logic App Designer.
  • Start with a common trigger like “When an HTTP request is received” if you want your Logic App to act based on external requests.
  • Add a new step by searching for “HTTP” in the actions list and choose the “HTTP – HTTP” action. This will be used to call the Azure OpenAI API.

Step 4: Configure the HTTP Action for Azure OpenAI

  • Method: POST
  • URI: Enter the endpoint URL of your Azure OpenAI service.
  • Headers: Add two headers:
    • Content-Type with the value application/json
    • Authorization with the value Bearer <Your Azure OpenAI API Key>
  • Body: Craft the JSON payload according to your task. For example, to generate text, your body might look like this:
{
  "prompt": "Write a brief about integrating Azure OpenAI with Logic Apps.",
  "temperature": 0.7,
  "max_tokens": 100
}

Step 5: Process the Response

After calling the Azure OpenAI API, you’ll want to handle the response:

  • Add a “Parse JSON” action to interpret the API response.
  • In the “Content” box, select the body of the HTTP action.
  • Define the schema based on the Azure OpenAI response format. For text generation, you’ll focus on extracting the generated text from the response.

Step 6: Add Final Actions

Decide what to do with the Azure OpenAI’s response. You could:

  • Send an email with the generated content.
  • Save the response to a database or a file in Azure Blob Storage.
  • Respond to the initial HTTP request with the generated content.

Step 7: Test Your Logic App

  • Save your Logic App and run a test by triggering it based on your chosen trigger method.
  • Monitor the run in the “Overview” section of your Logic App to ensure everything executes as expected.