naoki0311 (@naoki0311) header
naoki0311 (@naoki0311) profile picture

技術好きです。MSKKにてカスタマーサクセスに従事。 ここでの発言は私見が多分に含まれており、所属組織とは関係ありません。 cloud(Azure), community, M365とか多め。

日本
Joined June 2007
Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)Photo by naoki0311 (@naoki0311)
AIサービスの絶対原則だけ皆さんにお伝えします。 「「「 絶対に年額プランには入らない 」」」 絶対ダメです。
50
222
89
3,094
538,555
naoki0311 retweeted
思ったよりも需要がありそうだったので、先手必勝であげました。 下手なナレッジよりも効果的なCopilotChat + SKills + Sharepoint + MS Listによるナレッジサイクルです。 個人でもチームでも同じような運用ができ、Copilot Studioも不要で、今すぐに始められます。 大事なのは「育てる」ことです
6
43
11
551
36,297
あとMS環境でのこのやり方は、チームとか部単位で回すだけでも自然とナレッジとかノウハウ貯まるので、個人的には変にRAG作るより圧倒的に良いと思ってる。 どうせ毎日レベルで更新されていくので、まずはガンガン貯めてガンガンフィードバックしていきましょ。
Copilotとかでも自分だけのListとか作って、通常のCopilotChatのSKillsにListへのフィードバック更新機能つけておけば、 ・毎日の文句を全部Listへ入れる⇨未実施のものを全て改善フィードバックに回す⇨できたら実施済みに変更 これだけでもMS環境で同じように改善ループできるのでおすすめ。
1
9
1
212
13,737
教えてもらった内容を実装する際に、ただそのまま実装するのではなく、自分にとって必要な形でチューニングして組み込んでいけるのが、AI時代のいい点だよなぁって思う。 @yugen_matuni , @super_bonochin が話しているような、作りきることに拘るからこそ磨いていける。 #なんでもCopilot
1
202
naoki0311 retweeted
Copilotクレジット、事前購入の範囲内で使ってるフェーズが終わり、止まっては困るから従量課金で、というフェーズに変わってきた。 これは経営判断なんだよね。 従来の稟議やコストの考えに従うと使わせない設計になってしまう。 ザルにしろという訳ではない。信頼感の話かも。
3
2
34
4,646
書きました〜 1.1の方が先にGAしたので、もう1を使う理由はなさそうです。 Microsoft-Decision-1.1公開!Microsoft-Decision-1との差はどれくらい?|Junpei Tsuchida(07JP27) zenn.dev/microsoft/articles/… #zenn
10
2
23
1,650
本日、私のFDEチームで培ったベストプラクティスを基に、 Copilot Cowork 導入ガイドを Microsoft Learn に公開しました!(既に日本語化済み) どの業務をCoworkで行うか、どうやって自社システムと連携するか、実装から導入までを包括的に網羅してます! learn.microsoft.com/ja-jp/co…
5
69
4
462
28,917
Bringing Salesforce to Copilot as we build Copilot as the OS for work!
Introducing Copilotforce Salesforce customer context and sales workflows are coming to @MSFTCopilot and @MicrosoftTeams—where more than 400M people already collaborate Our expanded partnership with @Microsoft spans Copilot, Teams & Fabric: → Salesforce in Microsoft Copilot will help sellers prepare for meetings, spot deal risks & take supported Salesforce actions, informed by customer context, emails, meetings & shared documents → @SalesCloud in Teams will bring pipeline insights, deal alerts & supported opportunity updates into Teams, with Agentforce Coworker helping sellers delegate work & take action → Data 360 + Microsoft Fabric connect through bidirectional zero copy, so teams can access data across both platforms without duplicating source datasets → @Informatica expands its Microsoft integrations to help teams find trusted data in Copilot, build governed AI agents in Foundry & trace data lineage in Fabric @Accenture joins as Customer Zero and design and implementation partner to help shape and validate Copilotforce within its global sales organization, after scaling Microsoft Copilot to 740,000+ people See what’s new from #MSIgnite: sforce.co/4kgw4iZ
132
104
21
1,589
255,710
あかん。何かすっごく頭が働かない…
115
Copilot Chat だけでなく、Copilot in SharePoint の側のChat にもクレジットの消費量を見れる機能が追加されてる。 あとどのくらいクレジット使えるか確認できるのは安心感がある。
4
16
2,460
🍓15th Anniversary ラブライブ!フェス🍓 / #Liella! 「Hyper Glowing!」 本日21:00より一部プレミア公開✨ youtu.be/aW95vTmGCPM \ ”We are スーパースター!!” 🔽U-NEXT&イープラスの配信チケット 販売中! lovelive-anime.jp/special/li… #lovelive
18
2,553
555
5,956
602,363
naoki0311 retweeted
来年以降は対象を広げて、オープンなところでもやろうかなと思っています。例えば、ペンテストツールやコマンド動かしたら「答え」である応答返ってくるけど、それはWindowsのどの仕組みでどうなってるところを返してるの?を理解しとくのも重要かな、と思ってる次第で、
1
3
3
63
5,806
naoki0311 retweeted
Read this great blog from @OmarShahine - I love how he's built something new in a new way - while embracing with the best of Microsoft culture to dogfood the product to build the product every hour of the day
I’m incredibly proud of the Microsoft Autopilot Team. 7 months and 11 days ago our team had zero people and zero lines of code. In a short time we assembled some amazing AI builders in Microsoft to build something new. Today we are bringing the first enterprise-grade autonomous digital teammate to life. It has its own identity, email, OneDrive and works where you work. techcommunity.microsoft.com/…
2
4
55
4,449
naoki0311 retweeted
13 years after working at Microsoft, I had the pleasure to talk to @satyanadella at Ignite. My top 5 takeaways, lightly edited from his answers: 1. Can Microsoft catch up to the frontier labs? "This reminds me of a question when I was in Azure. People asked, 'Can you ever catch up with Amazon? Does anyone need a cloud other than Amazon?' My answer is the world will demand more than one cloud and model. What customers expect from [Microsoft] is flexibility and optionality, while delivering the tokens they need for their task with the economics in mind." 2. Do you have any advice for people who are anxious about how AI is changing work? From Satya: "My job is to turn that anxiety into restructuring Microsoft so we look like any new company. The new company looks like this: There's a founder. The founder has a token budget. Then the founder hires somebody, and they get a token budget too. All of Microsoft should look like that. All ICs are now managers of agents with a token budget. When people see that, I hope they say, oh, there's a path. The Copilot Cowork product is built by just 11 devs. And one developer builds and maintains the entire GitHub Copilot runtime." 3. What happens to software if it's primarily built for agents? "All of our business apps are now a headless plugin to Copilot. And they're used more than they ever were, because agents go in 24/7. I'm doing more CRM lookups than I ever did because I'm not doing it, my Autopilot is. Every day it looks at my OneNote and my meetings, pulls everything from Dynamics CRM for that customer, and checks the supply chain system. This 360-degree view was never possible before." 4. Do models get safer as they get smarter? "I used to think alignment would emerge as you scale. Based on empirical results, maybe not. So you need a trust architecture that's independent of the model, because the liability is all with us. That's why I like the metaphor of treating it like insider risk." 5. How should companies avoid getting locked into one model? "Assume the next model drop causes you to replan, so you don't build this massive thing around a model that becomes a boat anchor. What I'm trying to do is turn the model business into a database business. Use the model, but what you build on top is yours. Log what your agents do, use those traces to fine-tune, and when the next upgrade ships, fine-tune again and keep going." @satyanadella if you're reading this would love to go deeper on these topics sometime 🙂
32
21
1
341
33,563
今年は大きなアップデートもなく、寂しく部屋から1人お送りします、!ご興味ある方はぜひご参加ください。 日本時間15時からです。 #MSIgnite #MSIgniteJP events.teams.microsoft.com/e…
1
7
2
42
6,984
数字を達成するためのアプローチよりもシナリオ作ろうよ。。。
125
目的と手段間違えんなということを強く言いたい
1
317
なんか荒ぶりそうな感じが。。。
99
全国のお客様およびパートナーの皆様へ 先週発生した Microsoft 365 の障害により、お客様およびパートナーの皆様の日々の業務や事業運営に、多大なご迷惑とご心配をおかけしましたことを、改めまして心よりお詫び申し上げます。 本件は技術的な問題によるもので、サイバー攻撃または AI や AI エージェントに起因するものではありません。多くの Microsoft 365 サービスの前段に位置するネットワーク ゲートウェイにおいて、次の 3 つの要因が重なり、グローバル規模の障害に至りました。 第一に、特定の負荷条件下で、サーバーが過負荷となり応答不能に陥る潜在的な不具合がありました。これは、Microsoft 365 のネットワーク ゲートウェイ サーバー専用に用意した修正プログラムに起因するものです。この修正プログラムは本年 7 月から全世界へ順次展開され、3 か月以上にわたり、本不具合は顕在化していませんでした。 第二に、障害発生の約 15 時間前、Teams は、利用するネットワーク ゲートウェイを Exchange Online も利用しているプライマリ ゲートウェイへ切り替えました。これにより同ゲートウェイの負荷が増加し、トラフィックのパターンも変化しました。なお、この切り替えは、通常の運用手順に従ったものでした。 第三に、その時点で、前日に発生した別の問題により、ネットワーク ゲートウェイのサーバーの約 14% が停止していました。全体の処理能力には十分な余裕があったため、この停止だけではお客様への影響は確認されていませんでした。しかし、前述の切り替えによる負荷の集中と重なったことで、その余裕が大きく減少しました。 このように、負荷の増加とサーバー容量の減少が重なった結果、潜在していた不具合が顕在化しました。リクエストが滞留して最終的にサーバーが応答不能に陥り、障害は世界各地のネットワーク ゲートウェイ基盤へと連鎖的に拡大しました。また、通常より復旧に時間を要したのは、サービスを復旧したサーバーに、待機していたトラフィックが一斉に流れ込み、再び過負荷となったためです。当社は本不具合が原因であることを特定後、該当する処理を従来の正常な状態に戻すためのアップデートを開発し、サービスを段階的に復旧いたしました。 障害の発生以降、処理能力を増強するとともに、トラフィックのリダイレクトと接続処理に関する監視を強化しました。あわせて、影響の連鎖的な拡大を防ぐため、負荷を分散する制御策を導入しております。また、障害中に滞留したメールが配信不能として送信者に返送されないよう、メールの配信期限を延長いたしました。事後検証報告書(PIR)は、Microsoft 365 管理センターで公開しております。 お客様が当社サービスに寄せてくださる信頼に応える責任を、私たちは極めて重く受け止めています。今回の教訓を確実に生かし、再発防止に全力を尽くしてまいります。
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services. First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments. The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact. Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores. Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts. Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own. Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States. When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally. Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway. Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change. After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region). The final Post-Incident Review (PIR) will provide more details later this week.
33
1,488
104
2,767
416,729