r/SysAdminBlogs • • 23h ago

Entra Privilege Identity Management (PIM) - Role activation and more now possible at MyAccess

Thumbnail
blog.sonnes.cloud
7 Upvotes

From a feature request to Microsoft Ignite announcement – almost a year in the making!

Back in November 2025, I sent a feature suggestion directly to the Microsoft Entra engineering team: Why not bring Privileged Identity Management (PIM) role activation into the My Access portal?

An idea partly inspired by my findings around the hidden PIM URLs and undocumented UI experiences:

https://blog.sonnes.cloud/the-hidden-microsoft-entra-pim-urls-microsoft-never-documented-even-when-restrict-access-to-microsoft-entra-admin-center-is-enabled/

Fast forward almost a year… and here we are! 😎

I've had the opportunity to participate in the Private Preview, test the capabilities, share feedback and work closely with the team. Now it's officially announced in the Microsoft Ignite 2026 Book of News!

In my latest blog post, I share the story, hands-on testing, technical findings and a complete walkthrough, covering:
> PIM activation for Entra ID, Azure RBAC and Groups
> Just-in-Time (JIT) privileged access
> Remote Resource Access, Azure Bastion and Cloud Shell
> Requirements, limitations and findings not previously covered!

It's incredibly rewarding to see an idea evolve into an actual Microsoft product capability.

Sometimes, it's worth sending that email. You never know where it might lead! 😉

#Microsoft #EntraID #PIM #IdentitySecurity #MSIgnite #MicrosoftMVP #MVPBuzz #Community


r/SysAdminBlogs • • 21h ago

Global Secure Access - Device Access is here!

Thumbnail
blog.sonnes.cloud
4 Upvotes

Another Global Secure Access update - Device Access is here!

Bringing pre-logon connectivity back to Windows devices using device identity instead of user identity like we know from the old days!

Think on password changes, first-time sign-ins, domain controller connectivity, Group Policy processing and on-premises device management - all before a user signs in to Windows!

I've been following and testing this feature since its earlier preview in June 2026, and it's great to finally see it reach Public Preview at Microsoft Ignite.

In my latest blog post, I cover a lot - check it out!

#Microsoft #EntraID #GlobalSecureAccess #GSA #ZeroTrust #MSecurity #MSIgnite #MVP #MVPBuzz


r/SysAdminBlogs • • 5h ago

Terraform Modules: 5 practices that make infrastructure code easier to maintain

2 Upvotes

When working with Terraform in real infrastructure environments, writing working configuration is only one part of the job.

The bigger challenge is keeping infrastructure code reusable, maintainable, consistent, and easy for other engineers to understand.

For example, imagine multiple engineers managing VPCs, EC2 instances, and storage resources across different environments.

Without proper module design and version management, configurations can become difficult to maintain and changes can introduce unexpected issues.

Here are five practices worth following when building Terraform modules:

1. Keep modules small and focused

Separate networking, compute, and storage responsibilities instead of building one oversized module.

2. Use descriptive variable names

Avoid unclear names like v1 or x. Use meaningful names such as instance_type and ami_id.

3. Document modules properly

Include a README with usage examples, input variables, outputs, and requirements.

4. Use Git version control

Track module changes, maintain stable releases, and make rollbacks easier.

5. Manage access to shared modules

Use private repositories, access controls, and branch protection to manage infrastructure code securely.

I recently put together a practical guide covering these five Terraform module practices, with examples.

Full article:
https://datadevblog.com/terraform-modules-best-practices/

Discussion question:

For those managing Terraform in production, what causes the biggest maintenance problems in your modules?

Is it poor module design, version management, documentation, or something else?

Would love to hear your experiences.


r/SysAdminBlogs • • 10h ago

We're building a supercomputer

Thumbnail
golem.de
2 Upvotes

r/SysAdminBlogs • • 13h ago

A Linux time travel tool

Thumbnail
github.com
2 Upvotes

About a month ago I asked here if a tool to see ps, ss or lsof output at a past moment was worth building:

https://www.reddit.com/r/linuxadmin/comments/1wyhwfe/is_a_linux_time_travel_tool_worth_building/

I got some fair pushback (sar, atop, below, Prometheus, zabbix) and a few people who were curious. I looked at all of them. They cover a lot, but none of them could tell me which process had which connections open, or what lsof showed for a process at 02:45 last night. So I built it, mostly to find out if it could be done without hurting the server.

I wanted to name it "command line time travel" but then a though about the consequences of such a name and It's called clifr instead (command line flight recorder) and has two parts:

  • clifrd runs as a service and records processes, process starts and exits (through eBPF, so a process that lives 5 ms still shows up), TCP connections with the process that owns them, files held open, mounts, kernel messages and the usual system counters. It keeps 72 hours in /var/lib/clifr, 2 GB max.
  • clifr rebuilds the output of the normal commands for a past moment or a time range. It doesn't run the command, it rebuilds the output from the recording.clifr --at "02:45" "ps aux" clifr --since "02:00" --until "03:00" "ss -tanp dst 10.0.4.21 and dport = :5432" clifr --since "1 hour ago" events # starts, exits, OOM kills, mounts clifr diff --at "14:00" --at "14:20" "ss -ltnp"

There are about 40 commands so far: ps, top, pidstat, lsof, ss, netstat, free, vmstat, iostat, mpstat, df, ip, dmesg, systemctl list-units, lsblk, and more and all are 100% accurate.

The first thing people asked last time was the cost, so here are the numbers:

Quiet serverMixed loadBusy server
CPU0.35% of one core0.5-0.6% of one core1.9% of one core
RAM~90 MiB~80-120 MiB~290 MiB (335 max)
Disk~`20 MiB/day~100 MiB/day~4 GiB/day
Networknone, no ports opennonenone

Disk use depends heavily on how busy the server is.

clifr is not a monitoring tool and has no alerts. It's not a security audit tool either: it doesn't record file reads or writes, and root can stop it. It's for the "what was going on at 02:45" question, after the fact.

Status: it's a prototype, version 0.1.0. It hasn't run on a real production server yet (a friend starts one this week), and all the load has been synthetic. AGPL-3.0, no telemetry, nothing leaves the box.

So if you have a test or dev box (RHEL 8/9, Rocky, Alma), I'd really appreciate it if you tried it and told me what breaks or what looks wrong. The most useful thing for me is comparing what clifr shows with what you know was really happening.

I appreciate all your comments even if they are harsh


r/SysAdminBlogs • • 11h ago

Every service desk demo this quarter was AI, so we built a test from our own queue

1 Upvotes

Four service desk demos in six weeks and every one led with AI. We're about 3,500 people across three regions, so leadership wants a number before anything gets budget.

The one with the boldest claim was Atera's Robin, pitched as an AI technician that resolves up to 92% of tier 1 and complex tier 2 incidents. What sets it apart from the others is that it runs the fix itself, checks the result, and closes the ticket with notes on what it did. Hardware still comes back to us, and the approval rules for what it can touch are ours to write.

So we picked three categories from last quarter, password lockouts, print queues, and VPN client errors, and set one rule. A ticket only counts as resolved if no tech touched it and it wasn't reopened. That's the test every vendor gets on our data.


r/SysAdminBlogs • • 23h ago

Microsoft vs. Facebook outages: how do you test whether your recovery path is independent?

1 Upvotes

Microsoft’s November 13 incident report describes a network change that exposed a fault from an earlier capacity upgrade. In Facebook’s 2021 outage, a backbone failure led to the withdrawal of routes to its authoritative DNS servers, and engineers had trouble accessing recovery systems. Different failures, same question about shared dependencies.

If your primary network became unreachable, could you still resolve the names you need, authenticate, reach your management tools, and roll back the change? For those of you who’ve tested this end to end, what dependency surprised you?

I wrote up the comparison here: https://lippi.hu/microsoft-vs-facebook-leallas-en