[{"data":1,"prerenderedAt":645},["ShallowReactive",2],{"article-\u002Farticles\u002Fcopilot-shanai-kitei-edp":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"category":11,"author":12,"tags":13,"body":18,"_type":639,"_id":640,"_source":641,"_file":642,"_stem":643,"_extension":644},"\u002Farticles\u002Fcopilot-shanai-kitei-edp","articles",false,"","その社内規則、Copilotを禁止していますか？｜「外部AIへの機微情報投入禁止」とEDPの読み合わせ方","「社内規則で外部AIへの機微情報の投入が禁止されているため、Microsoft 365 Copilotは使えない」——本当にそうでしょうか。規程の禁止文言を分解し、エンタープライズデータ保護（EDP）の保護範囲と突き合わせて利用可否を整理する実務手順を解説します。","2026-08-31","M365 Copilot導入","K.S.ロジャース株式会社",[14,15,16,17],"Microsoft 365 Copilot","AIガバナンス","情報セキュリティ","社内規程",{"type":19,"children":20,"toc":628},"root",[21,29,34,47,52,59,64,103,115,121,126,170,175,181,186,239,245,250,289,294,303,315,321,333,345,350,395,400,406,411,464,476,482,487,548,553,558,609,623],{"type":22,"tag":23,"props":24,"children":25},"element","p",{},[26],{"type":27,"value":28},"text","「当社の規則では、外部AIへの機密情報の入力が禁止されています。だからCopilotは使えません」",{"type":22,"tag":23,"props":30,"children":31},{},[32],{"type":27,"value":33},"Microsoft 365 Copilot の導入検討で、実際に最も多く出会う\"壁\"がこれです。生成AIブームの初期に急いで作られた社内規則には、「外部AIサービスへの機微情報・顧客情報の投入を禁止する」といった条項が入っていることが多く、この文言が Copilot まで一律に止めてしまっています。",{"type":22,"tag":23,"props":35,"children":36},{},[37,39,45],{"type":27,"value":38},"しかし、この結論は多くの場合、",{"type":22,"tag":40,"props":41,"children":42},"strong",{},[43],{"type":27,"value":44},"規程の文言と Copilot の仕組みを突き合わせないまま出されています",{"type":27,"value":46},"。本記事では、規程の禁止条項が本当に恐れているものを分解し、Microsoft 365 Copilot のエンタープライズデータ保護（EDP: Enterprise Data Protection）の保護範囲と対応づけて、利用可否を整理する実務手順を解説します。",{"type":22,"tag":23,"props":48,"children":49},{},[50],{"type":27,"value":51},"なお本記事は一般的な整理の枠組みを示すものであり、最終的な判断は自社の規程の文言・契約条件・法務確認に基づいて行ってください。",{"type":22,"tag":53,"props":54,"children":56},"h2",{"id":55},"よくある膠着-禁止されているので使えないの内訳",[57],{"type":27,"value":58},"よくある膠着 ―「禁止されているので使えない」の内訳",{"type":22,"tag":23,"props":60,"children":61},{},[62],{"type":27,"value":63},"この膠着には典型的な構図があります。",{"type":22,"tag":65,"props":66,"children":67},"ul",{},[68,81,93,98],{"type":22,"tag":69,"props":70,"children":71},"li",{},[72,74,79],{"type":27,"value":73},"規則を作った時点で想定していたのは、",{"type":22,"tag":40,"props":75,"children":76},{},[77],{"type":27,"value":78},"個人アカウントで使う無償のチャットAI",{"type":27,"value":80},"（入力内容が事業者側に渡り、学習に使われ得るもの）",{"type":22,"tag":69,"props":82,"children":83},{},[84,86,91],{"type":27,"value":85},"その後に登場した Copilot のような",{"type":22,"tag":40,"props":87,"children":88},{},[89],{"type":27,"value":90},"テナント内で完結する企業向けAI",{"type":27,"value":92},"は、想定に入っていない",{"type":22,"tag":69,"props":94,"children":95},{},[96],{"type":27,"value":97},"規則の文言は「外部AI」「機微情報の投入」と広く書かれているため、読みようによっては Copilot も該当してしまう",{"type":22,"tag":69,"props":99,"children":100},{},[101],{"type":27,"value":102},"誰も判断の責任を取りたくないため、「グレーなら禁止」で止まる",{"type":22,"tag":23,"props":104,"children":105},{},[106,108,113],{"type":27,"value":107},"つまり問題は「Copilotが危険かどうか」ではなく、",{"type":22,"tag":40,"props":109,"children":110},{},[111],{"type":27,"value":112},"規程の文言が新しい実態に追いついていない",{"type":27,"value":114},"ことにあります。であれば、やるべきは文言と実態の読み合わせです。",{"type":22,"tag":53,"props":116,"children":118},{"id":117},"step-1禁止条項を分解する-その規則は何を恐れているか",[119],{"type":27,"value":120},"Step 1：禁止条項を分解する ― その規則は何を恐れているか",{"type":22,"tag":23,"props":122,"children":123},{},[124],{"type":27,"value":125},"「外部AIへの機微情報投入禁止」という条項が守ろうとしているものを分解すると、懸念は次の4つに集約されます。",{"type":22,"tag":127,"props":128,"children":129},"ol",{},[130,140,150,160],{"type":22,"tag":69,"props":131,"children":132},{},[133,138],{"type":22,"tag":40,"props":134,"children":135},{},[136],{"type":27,"value":137},"第三者への流出",{"type":27,"value":139}," ―― 入力したデータがAI事業者や他社に渡ってしまうのではないか",{"type":22,"tag":69,"props":141,"children":142},{},[143,148],{"type":22,"tag":40,"props":144,"children":145},{},[146],{"type":27,"value":147},"学習への利用",{"type":27,"value":149}," ―― 入力内容がAIモデルの学習に使われ、他社への回答に混ざって出てくるのではないか",{"type":22,"tag":69,"props":151,"children":152},{},[153,158],{"type":22,"tag":40,"props":154,"children":155},{},[156],{"type":27,"value":157},"アクセス統制の喪失",{"type":27,"value":159}," ―― 社内で権限管理していた情報が、AIを経由して権限のない人に見えてしまうのではないか",{"type":22,"tag":69,"props":161,"children":162},{},[163,168],{"type":22,"tag":40,"props":164,"children":165},{},[166],{"type":27,"value":167},"追跡不能",{"type":27,"value":169}," ―― 誰が何を入力したか分からず、事故時に調査・説明ができないのではないか",{"type":22,"tag":23,"props":171,"children":172},{},[173],{"type":27,"value":174},"自社の規程を読むときは、条文をこの4つの懸念に翻訳してください。「外部AI」という言葉自体が問題なのではなく、この4つが起きる形態のAI利用が問題なのだ、と整理できれば、判断基準が明確になります。",{"type":22,"tag":53,"props":176,"children":178},{"id":177},"step-2edpの保護範囲を確認する",[179],{"type":27,"value":180},"Step 2：EDPの保護範囲を確認する",{"type":22,"tag":23,"props":182,"children":183},{},[184],{"type":27,"value":185},"Microsoft 365 Copilot（および M365 アカウントでサインインした Copilot Chat）には、エンタープライズデータ保護（EDP）が適用されます。ポイントは5つです。",{"type":22,"tag":65,"props":187,"children":188},{},[189,199,209,219,229],{"type":22,"tag":69,"props":190,"children":191},{},[192,197],{"type":22,"tag":40,"props":193,"children":194},{},[195],{"type":27,"value":196},"契約境界内での処理",{"type":27,"value":198}," ―― プロンプト（入力）と応答は自社のMicrosoft 365テナントの契約条件の下で扱われ、SharePointのファイルやExchangeのメールと同じ契約的保護を受けます",{"type":22,"tag":69,"props":200,"children":201},{},[202,207],{"type":22,"tag":40,"props":203,"children":204},{},[205],{"type":27,"value":206},"暗号化",{"type":27,"value":208}," ―― データは保存時・転送時ともに暗号化されます",{"type":22,"tag":69,"props":210,"children":211},{},[212,217],{"type":22,"tag":40,"props":213,"children":214},{},[215],{"type":27,"value":216},"テナント間の分離",{"type":27,"value":218}," ―― 自社のデータが他社のテナントと混ざることはありません",{"type":22,"tag":69,"props":220,"children":221},{},[222,227],{"type":22,"tag":40,"props":223,"children":224},{},[225],{"type":27,"value":226},"基盤モデルの学習に使われない",{"type":27,"value":228}," ―― プロンプトと応答が、基盤となるAIモデルの学習に利用されることはありません",{"type":22,"tag":69,"props":230,"children":231},{},[232,237],{"type":22,"tag":40,"props":233,"children":234},{},[235],{"type":27,"value":236},"権限の継承",{"type":27,"value":238}," ―― Copilotはユーザー本人が閲覧権限を持つデータしか参照・出力しません。また利用は監査ログに記録され、Microsoft Purview による追跡・eDiscoveryの対象にできます",{"type":22,"tag":53,"props":240,"children":242},{"id":241},"step-3懸念と保護範囲を対応づける",[243],{"type":27,"value":244},"Step 3：懸念と保護範囲を対応づける",{"type":22,"tag":23,"props":246,"children":247},{},[248],{"type":27,"value":249},"Step 1 の4つの懸念に、Step 2 の保護範囲を当てはめます。",{"type":22,"tag":127,"props":251,"children":252},{},[253,262,271,280],{"type":22,"tag":69,"props":254,"children":255},{},[256,260],{"type":22,"tag":40,"props":257,"children":258},{},[259],{"type":27,"value":137},{"type":27,"value":261}," → プロンプト・応答はテナントの契約境界内に留まります。無償チャットAIへの「貼り付け」とは、データの置かれる場所が契約上まったく異なります",{"type":22,"tag":69,"props":263,"children":264},{},[265,269],{"type":22,"tag":40,"props":266,"children":267},{},[268],{"type":27,"value":147},{"type":27,"value":270}," → EDPの下では基盤モデルの学習に使われません",{"type":22,"tag":69,"props":272,"children":273},{},[274,278],{"type":22,"tag":40,"props":275,"children":276},{},[277],{"type":27,"value":157},{"type":27,"value":279}," → 既存のアクセス権限がそのまま継承されます。閲覧権限のないデータをAIが引用することは構造的に起きません",{"type":22,"tag":69,"props":281,"children":282},{},[283,287],{"type":22,"tag":40,"props":284,"children":285},{},[286],{"type":27,"value":167},{"type":27,"value":288}," → 監査ログとPurviewで、誰がいつ何に使ったかを追跡できます",{"type":22,"tag":23,"props":290,"children":291},{},[292],{"type":27,"value":293},"この対応づけができると、次の整理が可能になります。",{"type":22,"tag":295,"props":296,"children":297},"blockquote",{},[298],{"type":22,"tag":23,"props":299,"children":300},{},[301],{"type":27,"value":302},"当社規程が禁止する「外部AIへの機微情報の投入」とは、入力データが契約的保護の外に出て、第三者提供・学習利用され得る形態を指す。エンタープライズデータ保護が適用された Microsoft 365 Copilot の利用は、データが自社テナントの契約境界内で処理されるため、この「外部への投入」には該当しないと整理する。",{"type":22,"tag":23,"props":304,"children":305},{},[306,308,313],{"type":27,"value":307},"「Copilotは規則違反ではない」と主張するのではなく、",{"type":22,"tag":40,"props":309,"children":310},{},[311],{"type":27,"value":312},"規則が守ろうとしているものをCopilotの仕組みが満たしている",{"type":27,"value":314},"ことを示す——これが通る説明の型です。",{"type":22,"tag":53,"props":316,"children":318},{"id":317},"step-4ただしこの整理には条件がある",[319],{"type":27,"value":320},"Step 4：ただし、この整理には条件がある",{"type":22,"tag":23,"props":322,"children":323},{},[324,326,331],{"type":27,"value":325},"ここまでの整理は、Microsoftが担保する層の話です。見落としてはいけないのは、",{"type":22,"tag":40,"props":327,"children":328},{},[329],{"type":27,"value":330},"EDPが守ってくれない領域が自社側に残る",{"type":27,"value":332},"ことです。",{"type":22,"tag":23,"props":334,"children":335},{},[336,338,343],{"type":27,"value":337},"最大の論点は「権限の継承」の裏返しです。Copilotはユーザーが開ける情報をすべて探しに行くため、",{"type":22,"tag":40,"props":339,"children":340},{},[341],{"type":27,"value":342},"SharePointの共有設定がずさんなら、そのずさんさがそのままAIの回答に反映されます",{"type":27,"value":344},"。「全社共有」に置かれたままの人事資料や役員会議事録は、権限上は\"全員が閲覧可能\"であり、Copilotは正しくそれを引用します。これはEDPの欠陥ではなく、自社の権限設計の問題です。",{"type":22,"tag":23,"props":346,"children":347},{},[348],{"type":27,"value":349},"つまり Step 3 の整理が実務として成立するのは、次の整備が伴っているときです。",{"type":22,"tag":65,"props":351,"children":352},{},[353,363,373,383],{"type":22,"tag":69,"props":354,"children":355},{},[356,358],{"type":27,"value":357},"SharePoint\u002FOneDrive の",{"type":22,"tag":40,"props":359,"children":360},{},[361],{"type":27,"value":362},"アクセス権の棚卸しと過剰共有の是正",{"type":22,"tag":69,"props":364,"children":365},{},[366,368],{"type":27,"value":367},"Microsoft Purview による",{"type":22,"tag":40,"props":369,"children":370},{},[371],{"type":27,"value":372},"秘密度ラベル等の機密区分の設計",{"type":22,"tag":69,"props":374,"children":375},{},[376,381],{"type":22,"tag":40,"props":377,"children":378},{},[379],{"type":27,"value":380},"利用ガイドライン",{"type":27,"value":382},"の策定と利用者教育",{"type":22,"tag":69,"props":384,"children":385},{},[386,388,393],{"type":27,"value":387},"監査ログを",{"type":22,"tag":40,"props":389,"children":390},{},[391],{"type":27,"value":392},"実際に見る運用",{"type":27,"value":394},"の設計",{"type":22,"tag":23,"props":396,"children":397},{},[398],{"type":27,"value":399},"「Microsoftが守る層」と「自社が設計する層」の二層構造で捉え、後者の整備計画とセットで提示することが、法務・経営の納得を得る条件になります。",{"type":22,"tag":53,"props":401,"children":403},{"id":402},"step-5法務経営への説明ドキュメントを作る",[404],{"type":27,"value":405},"Step 5：法務・経営への説明ドキュメントを作る",{"type":22,"tag":23,"props":407,"children":408},{},[409],{"type":27,"value":410},"社内説明用のドキュメントは、次の構成をおすすめします。A4で2〜3枚に収まります。",{"type":22,"tag":127,"props":412,"children":413},{},[414,424,434,444,454],{"type":22,"tag":69,"props":415,"children":416},{},[417,422],{"type":22,"tag":40,"props":418,"children":419},{},[420],{"type":27,"value":421},"規程の該当条文の引用",{"type":27,"value":423},"と、条文が防ごうとしている4つの懸念への分解",{"type":22,"tag":69,"props":425,"children":426},{},[427,432],{"type":22,"tag":40,"props":428,"children":429},{},[430],{"type":27,"value":431},"懸念とEDPの保護範囲の対応表",{"type":27,"value":433},"（懸念ごとに、何によって担保されるかを1行ずつ）",{"type":22,"tag":69,"props":435,"children":436},{},[437,442],{"type":22,"tag":40,"props":438,"children":439},{},[440],{"type":27,"value":441},"自社側で整備する事項と時期",{"type":27,"value":443},"（権限棚卸し・ラベル設計・ガイドライン・教育）",{"type":22,"tag":69,"props":445,"children":446},{},[447,452],{"type":22,"tag":40,"props":448,"children":449},{},[450],{"type":27,"value":451},"利用範囲の段階設計",{"type":27,"value":453}," ―― まず機微情報を含まない業務（議事録要約・文書ドラフト・メール下書きなど）から開始し、整備の進捗に応じて範囲を広げる。拡大の判断は都度、会社として行う",{"type":22,"tag":69,"props":455,"children":456},{},[457,462],{"type":22,"tag":40,"props":458,"children":459},{},[460],{"type":27,"value":461},"規程改定の提案",{"type":27,"value":463},"（次項）",{"type":22,"tag":23,"props":465,"children":466},{},[467,469,474],{"type":27,"value":468},"この「段階設計」が重要です。整理がついても、初日から機微情報を扱う業務に使う必要はありません。",{"type":22,"tag":40,"props":470,"children":471},{},[472],{"type":27,"value":473},"非機微業務で開始 → 整備 → 段階拡大",{"type":27,"value":475},"という順序を示すことで、承認のハードルは大きく下がります。",{"type":22,"tag":53,"props":477,"children":479},{"id":478},"step-6規程の改定-グレーを残さない",[480],{"type":27,"value":481},"Step 6：規程の改定 ― グレーを残さない",{"type":22,"tag":23,"props":483,"children":484},{},[485],{"type":27,"value":486},"読み合わせで運用を始められても、規程の文言がそのままでは、判断が属人的なままです。最後に規程自体を改定し、明文化します。盛り込むべきは次の観点です。",{"type":22,"tag":65,"props":488,"children":489},{},[490,502,514,524,536],{"type":22,"tag":69,"props":491,"children":492},{},[493,495,500],{"type":27,"value":494},"「外部AI」の定義を、",{"type":22,"tag":40,"props":496,"children":497},{},[498],{"type":27,"value":499},"データの取り扱い条件",{"type":27,"value":501},"（契約的保護の有無、学習利用の有無、テナント内処理か否か）で定義し直す",{"type":22,"tag":69,"props":503,"children":504},{},[505,507,512],{"type":27,"value":506},"会社が承認したAIサービスの",{"type":22,"tag":40,"props":508,"children":509},{},[510],{"type":27,"value":511},"リスト管理方式",{"type":27,"value":513},"にする（サービス名を条文に直書きしない。改定が追いつかなくなります）",{"type":22,"tag":69,"props":515,"children":516},{},[517,522],{"type":22,"tag":40,"props":518,"children":519},{},[520],{"type":27,"value":521},"個人アカウントでの業務利用の禁止",{"type":27,"value":523},"を明記する",{"type":22,"tag":69,"props":525,"children":526},{},[527,529,534],{"type":27,"value":528},"機微情報の利用可否は",{"type":22,"tag":40,"props":530,"children":531},{},[532],{"type":27,"value":533},"秘密度ラベル等の機密区分と紐づけて",{"type":27,"value":535},"規定する",{"type":22,"tag":69,"props":537,"children":538},{},[539,541,546],{"type":27,"value":540},"新しいAIサービスを使いたい場合の",{"type":22,"tag":40,"props":542,"children":543},{},[544],{"type":27,"value":545},"申請・審査フロー",{"type":27,"value":547},"を定める",{"type":22,"tag":23,"props":549,"children":550},{},[551],{"type":27,"value":552},"なお、MicrosoftのサービスやEDPの仕様は変化し続けます。整理した内容は「作成時点の仕様に基づく」ことを明記し、年1回以上の見直しをルール化しておくことをおすすめします。",{"type":22,"tag":53,"props":554,"children":556},{"id":555},"まとめ",[557],{"type":27,"value":555},{"type":22,"tag":65,"props":559,"children":560},{},[561,573,592,604],{"type":22,"tag":69,"props":562,"children":563},{},[564,566,571],{"type":27,"value":565},"「規則で禁止されているのでCopilotは使えない」の多くは、",{"type":22,"tag":40,"props":567,"children":568},{},[569],{"type":27,"value":570},"規程の文言が実態に追いついていない",{"type":27,"value":572},"だけです",{"type":22,"tag":69,"props":574,"children":575},{},[576,578,583,585,590],{"type":27,"value":577},"禁止条項を",{"type":22,"tag":40,"props":579,"children":580},{},[581],{"type":27,"value":582},"4つの懸念",{"type":27,"value":584},"（流出・学習利用・統制喪失・追跡不能）に分解し、",{"type":22,"tag":40,"props":586,"children":587},{},[588],{"type":27,"value":589},"EDPの保護範囲",{"type":27,"value":591},"と対応づければ、「外部への投入には当たらない」という整理が可能です",{"type":22,"tag":69,"props":593,"children":594},{},[595,597,602],{"type":27,"value":596},"ただしこの整理は、",{"type":22,"tag":40,"props":598,"children":599},{},[600],{"type":27,"value":601},"自社側の整備",{"type":27,"value":603},"（権限・ラベル・ガイドライン）が伴って初めて成立します",{"type":22,"tag":69,"props":605,"children":606},{},[607],{"type":27,"value":608},"最後は規程を改定し、グレーゾーンを残さないことが重要です",{"type":22,"tag":23,"props":610,"children":611},{},[612,614,621],{"type":27,"value":613},"Copilot導入の全体像は",{"type":22,"tag":615,"props":616,"children":618},"a",{"href":617},"\u002Farticles\u002Fm365-copilot-donyu-roadmap\u002F",[619],{"type":27,"value":620},"第1回：非IT企業のMicrosoft 365 Copilot導入ロードマップ",{"type":27,"value":622},"で解説しています。",{"type":22,"tag":23,"props":624,"children":625},{},[626],{"type":27,"value":627},"K.S.Rogers では、規程とEDPの読み合わせ整理、経営・法務向け説明資料の作成、SharePoint・Purviewの整備からガイドライン策定までを一貫して支援しています。「規則の壁」で止まっている方は、ぜひ一度ご相談ください。",{"title":7,"searchDepth":629,"depth":629,"links":630},2,[631,632,633,634,635,636,637,638],{"id":55,"depth":629,"text":58},{"id":117,"depth":629,"text":120},{"id":177,"depth":629,"text":180},{"id":241,"depth":629,"text":244},{"id":317,"depth":629,"text":320},{"id":402,"depth":629,"text":405},{"id":478,"depth":629,"text":481},{"id":555,"depth":629,"text":555},"markdown","content:articles:copilot-shanai-kitei-edp.md","content","articles\u002Fcopilot-shanai-kitei-edp.md","articles\u002Fcopilot-shanai-kitei-edp","md",1788174921268]