Search results

최근 Microsoft가 집중적으로 개발하고 있는 Microsoft Foundry의 주요 기능 중 하나인 Hosted Agent는 Microsoft 스타일의 PaaS 개발의 정수를 보여주는 방식으로 기능이 개발되어가고 있습니다.

이는 Azure Function이나 예전 Windows Azure 시절 (Microsoft Azure로 리브랜딩되기 이전인 극 초창기 Azure 브랜드)의 Compute Role을 생각나게 하는 부분인데, Hosted Agent의 최신 기능을 살펴보면서 다른 한편으로 Microsoft의 기술 철학에 대해 이야기하는 아티클을 작성해보았습니다.

https://devwrite.ai/ko/posts/hosted-agent-deep-dive/

1

📰 PRを送るだけでリポジトリを「乗っ取れる」?GitHub Actionsの危ない書き方を実際に検証してみた (hackerbot-claw) (👍 47)

🇬🇧 AI bot 'hackerbot-claw' exploited GitHub Actions vulnerabilities, achieving RCE on 4/7 targets. Demonstrates dangerous workflow patterns.
🇰🇷 AI 봇 'hackerbot-claw'가 GitHub Actions 취약점을 악용해 7개 중 4개 타겟에서 RCE 성공. 위험한 워크플로우 패턴 실증.

🔗 zenn.dev/aeyesec/articles/4175

📰 あなたはEntra IDを理解できる (👍 39)

🇬🇧 Beginner-friendly guide to Microsoft Entra ID (formerly Azure AD). Explains cloud identity management abstraction with practical examples.
🇰🇷 Microsoft Entra ID(구 Azure AD) 입문 가이드. 클라우드 ID 관리 추상화를 실용적 예시로 설명.

🔗 zenn.dev/headwaters/articles/6

0

🕐 2026-03-03 12:00 UTC

📰 Async React時代の宣言的UI: デバウンスの例 (👍 67)

🇬🇧 Explores declarative UI in async React, showing how to handle debouncing declaratively instead of imperatively for cleaner code
🇰🇷 비동기 React의 선언적 UI 탐구, 디바운싱을 명령형 대신 선언적으로 처리해 깔끔한 코드 작성하는 방법 소개

🔗 zenn.dev/uhyo/articles/async-r

📰 あなたはEntra IDを理解できる (👍 37)

🇬🇧 Beginner-friendly guide to Microsoft Entra ID, explaining cloud identity management with concrete usage examples for Azure newcomers
🇰🇷 Microsoft Entra ID 초보자 가이드, Azure 입문자를 위한 클라우드 ID 관리를 구체적 예시로 설명

🔗 zenn.dev/headwaters/articles/6

0

📰 VS Code + GitHub Copilot で並列タスクが快適になったので、やり方を整理する (👍 31)

🇬🇧 VS Code v1.109's new agent session management UI makes parallel tasks with GitHub Copilot much smoother and easier to track.
🇰🇷 VS Code v1.109의 새 에이전트 세션 관리 UI로 GitHub Copilot 병렬 작업이 훨씬 편리해졌습니다.

🔗 zenn.dev/shinkawa/articles/d9f

📰 あなたはEntra IDを理解できる (👍 30)

🇬🇧 Understanding Microsoft Entra ID (formerly Azure AD) — a cloud-based identity management service explained for beginners.
🇰🇷 Microsoft Entra ID(구 Azure AD) — 클라우드 기반 ID 관리 서비스를 초보자도 이해할 수 있게 설명합니다.

🔗 zenn.dev/headwaters/articles/6

0

📰 セキュリティって難しい (👍 46)

🇬🇧 Explores structural challenges of enterprise security beyond just technical knowledge - why understanding systems deeply is critical
🇰🇷 기술 지식을 넘어 기업 보안의 구조적 어려움 탐구 - 시스템을 깊이 이해해야 하는 이유

🔗 zenn.dev/mizutani/articles/sec

📰 あなたはEntra IDを理解できる (👍 29)

🇬🇧 Demystifying Microsoft Entra ID (Azure AD) - understand cloud authentication abstraction with practical examples for beginners
🇰🇷 Microsoft Entra ID (Azure AD) 쉽게 이해하기 - 초보자를 위한 실용적 예제로 클라우드 인증 추상화 설명

🔗 zenn.dev/headwaters/articles/6

0
0
0
0

I'd argue that very few companies have any real appreciation for how many of their employees are already feeding API keys and other stuff into fairly new and questionable agentic AI tools or platforms. So many companies are like, oh we're taking a wait-and-see approach to adopting AI. Meanwhile, half their dev team is doing critical development work on shared servers that have no authentication or limited (no 2fa) auth.

@briankrebs@infosec.exchange

On the plus side, step #1 of setting up things like an
// account — especially production ones — is to disable the ability to create IAM users (forcing the use of IAM-roles that are 2FA authenticated via a service like ) …and the role-based authentication-tokens are typically TTLed to a couple hours.

Still, a "good" (suspicious-quotes) agent-setup would be pretty trivial to configure to snarf credentials from the relevant token-services. That triviality likely applies more broadly.

0

RE: infosec.exchange/@david_chisna

Wow, and support is terrible. It sends you to Copilot. Copilot says: 'If the resource group remains in the "MovingResources" state and you cannot identify any issues, it may be necessary to contact Azure Support. They can investigate backend issues and provide assistance in resolving the problem.'

Contacting support requires selecting from a drop-down list of common problems which does not include this problem. And there is no path I have yet found via their UI that actually seems to result in raising a support request.

Imagine trying to use this for important things!

0
0

Dew Drop – February 10, 2026 (#4601)

Morning Dew by Alvin Ashcraft – Daily links for Windows and .NET developers. @alvinashcraft.com@web.brid.gy

Top Links Ralph Wiggum Explained: Stop Telling AI What You Want — Tell It What Blocks You (Matt Mattei) Testing ads in ChatGPT (OpenAI Team) – And it begins… Strengthening Windows trust and security through User Transparency and Consent (Logan Iyer) AI Doesn’t Reduce Work—It Intensifies It (Simon Willison) How to Set Up Claude Code … Continue reading Dew Drop – February 10, 2026 (#4601)

Read more →
0
0
0

I just learned this week about the Global PyLadies Conference—happening virtually this Fri & Sat Dec 5th and 6th.

And Dawn Wages @BajoranEngineerdawn is one of the keynoters!

And Dingding Lu + Gauri Kasar (who I know from the Postgres team on Azure) are teaching a 1.5 hour workshop titled "Build Agentic AI with Semantic Kernel and Graph RAG on PostgreSQL" (on Sat Dec 6th at 10am PST)

I suppose it's not a surprise to see at a conference!

If you're just learning about this PyLadies conference, check out the schedule! And here is the link to Dingding and Gauri's workshop re Postgres: pretalx.com/pyladiescon-2025/t

PyLadiesCon 2025 poster with bio pics of Gauri Kasar and Dingding Lu from MIcrosoft, along with the title of their 1.5 hour workshop: "Build Agentic AI with Semantic Kernel and GraphRAG on PostgreSQL"
0

Cascading failure. It cascaded.

> As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy.
azure.status.microsoft/en-us/s

> An inadvertent tenant configuration change within Azure Front Door (AFD) triggered a widespread service disruption…

> The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations.

Am I reading this right? Global – pardon, "non-regional" – of was caused by a tenant changing their config? 👀

0

This might be a good time to consider deploying, contributing to or otherwise supporting @nextcloudNextcloud 📱☁️💻:
nextcloud.com/

And before anyone says that Nextcloud's UI/UX is lacking: of course it is! Nextcloud has several orders of magnitude less money to throw at UI/UX.

But guess what:
1. this is fixable if they get more resources to work with;
2. every single Nextcloud instance I know of or use (there are many) stayed up and running yesterday.

:blobcat:

Cascading failure. It cascaded.

> As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy.
azure.status.microsoft/en-us/s

0

This might be a good time to consider deploying, contributing to or otherwise supporting @nextcloudNextcloud 📱☁️💻:
nextcloud.com/

And before anyone says that Nextcloud's UI/UX is lacking: of course it is! Nextcloud has several orders of magnitude less money to throw at UI/UX.

But guess what:
1. this is fixable if they get more resources to work with;
2. every single Nextcloud instance I know of or use (there are many) stayed up and running yesterday.

:blobcat:

0
0
0

While Azure was down and you could not use your Office 365 for 8 (eight) hours yesterday, Microsoft was gloating about record profits:
theguardian.com/technology/202

After all, Office 365 price has increased at least twice over the last 12 months, massively:
tomsguide.com/computing/micros
techcommunity.microsoft.com/bl

Price hikes were due to "AI", obviously. It's what users crave. :blobcatpeek:

Your Microsoft Tax dollars at work! :blobcatcoffee:

Scene from Idiocracy, Attorney General speaking.

Text:

Microsoft's got what users crave. It's got AI.
0
0
0
0
0
0
0
0
0