[{"data":1,"prerenderedAt":1048},["ShallowReactive",2],{"sc:header-data-ja":3,"sc:footer-data-ja":178,"post-ja--posts-microsoft-cloud-pki-alternatives-1c5fb0f901c5c5":244,"authors_data":840,"authors_data:SCEPman Team":924,"content-ja-list-7b291c2dd91a4":926},{"lang":4,"home":5,"navigation":14},"en",{"name":6,"imgLight":7,"img":8,"languages":9},"home","/products/scepman/scepman-logo-all-white.svg","/products/scepman/scepman-logo-rgb.svg",{"ja":10},{"title":11,"url":12,"alt":13},"ホーム","/ja","SCEPman",[15,59,102,108,172],{"name":16,"languages":17,"children":20},"certificates",{"ja":18},{"title":19},"証明書",[21],{"name":22,"children":23},"certificates-group-1",[24,31,38,45,52],{"name":25,"languages":26},"network",{"ja":27},{"title":28,"url":29,"description":30},"Wi-Fi、LAN、VPN","/ja/certificate-network-authentication","ログインのたびに確認されるデバイス証明書とユーザー証明書",{"name":32,"languages":33},"servers",{"ja":34},{"title":35,"url":36,"description":37},"サーバーと Linux","/ja/internal-servers-certificates","EST、REST API、PowerShell、Certificate Master",{"name":39,"languages":40},"mfa",{"ja":41},{"title":42,"url":43,"description":44},"フィッシング耐性のある MFA","/ja/phishing-resistant-mfa","Entra の証明書ベース認証と YubiKey",{"name":46,"languages":47},"code-signing",{"ja":48},{"title":49,"url":50,"description":51},"コード署名","/ja/sign-your-code","デバイスがすでに信頼しているスクリプトとマクロ",{"name":53,"languages":54},"iot",{"ja":55},{"title":56,"url":57,"description":58},"IoT デバイス","/ja/iot-device-authentication","組み立てラインで発行する ECC 証明書",{"name":60,"languages":61,"children":64},"solutions",{"ja":62},{"title":63},"ソリューション",[65],{"name":66,"children":67},"solutions-group-1",[68,75,82,88,95],{"name":69,"languages":70},"intune",{"ja":71},{"title":72,"url":73,"description":74},"Microsoft Intune","/ja/mdms/pki-certificate-management-microsoft-intune-mdm","削除、無効化、ワイプで失効",{"name":76,"languages":77},"jamf",{"ja":78},{"title":79,"url":80,"description":81},"Jamf Pro","/ja/mdms/pki-certificate-management-jamf-pro-mdm","コンピューター、モバイルデバイス、ユーザー",{"name":83,"languages":84},"other-mdms",{"ja":85},{"title":86,"url":87},"その他の MDM","/ja/mdms/pki-certificate-management-other-mdms",{"name":89,"languages":90},"replace-adcs",{"ja":91},{"title":92,"url":93,"description":94},"ADCS の置き換え","/ja/replace-adcs","グループ ポリシーによる自動登録とドメイン コントローラー",{"name":96,"languages":97},"bundle",{"ja":98},{"title":99,"url":100,"description":101},"RADIUSaaS とのバンドル","/ja/secure-network-access-bundle","当社が運用する SCEPman、またはお客様のテナントで",{"name":103,"languages":104},"pricing",{"ja":105},{"title":106,"url":107},"価格","/ja/pricing",{"name":109,"languages":110,"children":113},"support-hub",{"ja":111},{"title":112},"Support Hub",[114,142,157],{"name":115,"children":116},"support-hub-group-1",[117,124,130,136],{"name":118,"target":119,"languages":120},"docs","_blank",{"ja":121},{"title":122,"url":123},"Docs","https://docs.scepman.com/",{"name":125,"languages":126},"faq",{"ja":127},{"title":128,"url":129},"FAQ","/ja/faq",{"name":131,"languages":132},"glossary",{"ja":133},{"title":134,"url":135},"用語集","/ja/glossary",{"name":137,"languages":138},"blog",{"ja":139},{"title":140,"url":141},"ブログ","/ja/blog",{"name":143,"children":144},"support-hub-group-2",[145,151],{"name":146,"languages":147},"events",{"ja":148},{"title":149,"url":150},"イベント","/ja/events",{"name":152,"languages":153},"partner",{"ja":154},{"title":155,"url":156},"パートナー","/ja/partner",{"name":158,"children":159},"support-hub-group-3",[160,166],{"name":161,"target":119,"languages":162},"support-ticket",{"ja":163},{"title":164,"url":165},"Support ticket","https://support.scepman.com/support/tickets/new?ticket_form=technical_support_request_%28scepman%29",{"name":167,"target":119,"languages":168},"drop-a-question",{"ja":169},{"title":170,"url":171},"Contact sales","https://support.scepman.com/support/tickets/new?ticket_form=drop_a_question_%28scepman%29",{"name":173,"languages":174},"about",{"ja":175},{"title":176,"url":177},"会社概要","/ja/about-us",{"data":179},{"mail":180,"logos":181,"socials":186,"linksEn":199,"links":223,"linksJa":232},"sales@SCEPman.com",[182],{"img":183,"alt":184,"url":185},"/products/scepman/scepman-logo-yellow.svg","SCEPman Logo","/",[187,191,195],{"icon":188,"url":189,"title":190},"fa-x-twitter","https://twitter.com/scepman_","X",{"icon":192,"url":193,"title":194},"fa-youtube","https://www.youtube.com/channel/UCKnLYxlQFhzdXkDADV_Unrg","Youtube",{"icon":196,"url":197,"title":198},"fa-linkedin","https://www.linkedin.com/showcase/scepman","LinkedIn",[200,202,205,208,211,214,217,220],{"title":128,"url":201},"/en/faq",{"title":203,"url":204},"Glossary","/en/glossary",{"title":206,"url":207},"Blog","/en/blog",{"title":209,"url":210},"Events","/en/events",{"title":212,"url":213},"Partner","/en/partner",{"title":215,"url":216,"target":119},"Privacy","https://www.glueckkanja.com/en/privacy",{"title":218,"url":219,"target":119},"Imprint","https://www.glueckkanja.com/en/imprint",{"title":221,"url":222,"target":119},"Contact & Locations","https://www.glueckkanja.com/en/company/contact-and-locations",[224,225,226,227,228,229,230,231],{"title":128,"url":201},{"title":203,"url":204},{"title":206,"url":207},{"title":209,"url":210},{"title":212,"url":213},{"title":215,"url":216,"target":119},{"title":218,"url":219,"target":119},{"title":221,"url":222,"target":119},[233,234,235,236,237,238,240,242],{"title":128,"url":129},{"title":134,"url":135},{"title":140,"url":141},{"title":149,"url":150},{"title":155,"url":156},{"title":239,"url":216,"target":119},"プライバシー",{"title":241,"url":219,"target":119},"法的情報",{"title":243,"url":222,"target":119},"お問い合わせと拠点",{"id":245,"title":246,"author":247,"body":249,"cta":794,"description":255,"eventid":794,"extension":795,"hideInRecent":796,"layout":797,"meta":798,"moment":801,"navigation":831,"path":833,"seo":834,"stem":835,"tags":836,"webcast":796,"__hash__":839},"content_ja/posts/microsoft-cloud-pki-alternatives.md","2026年のMicrosoft Cloud PKI代替ソリューション",[248],"SCEPman Team",{"type":250,"value":251,"toc":762},"minimal",[252,256,259,262,267,270,277,290,294,297,301,315,319,330,334,339,342,350,354,360,461,465,468,472,475,479,482,486,489,493,496,528,532,535,591,594,598,601,612,615,618,621,625,628,642,645,659,662,665,668,671,674,678,681,685,702,706,710,727,731,734,738,741,745,748,752,755,759],[253,254,255],"p",{},"Microsoft Cloud PKIは、Intuneで管理するデバイスへ証明書を発行するために設計されています。Microsoft中心の環境におけるモバイル管理やエンドポイント管理では、十分に機能します。",[253,257,258],{},"サーバー、Linux、ネットワーク機器、IoT、手動発行、ハイブリッドなActive Directory環境まで証明書の対象を広げたい場合は、すぐに限界に突き当たります。",[253,260,261],{},"このページでは、Intuneだけでは足りない範囲の証明書対応を必要とするチームに向けて、最も現実的なMicrosoft Cloud PKIの代替を取り上げます。",[263,264,266],"h2",{"id":265},"microsoft-cloud-pkiとは","Microsoft Cloud PKIとは",[253,268,269],{},"Microsoft Cloud PKIは、Microsoft Intuneに統合されたクラウドベースの認証局（CA）です。オンプレミスの基盤を運用せずに、管理下のデバイスへ証明書を発行できます。",[253,271,272,276],{},[273,274,275],"strong",{},"代表的なユースケース","：",[278,279,280,284,287],"ul",{},[281,282,283],"li",{},"Intuneで管理するエンドポイント（Windows、macOS、iOS、Android）",[281,285,286],{},"証明書によるWi-FiおよびVPNの認証",[281,288,289],{},"Microsoft環境における基本的なデバイスID",[263,291,293],{"id":292},"microsoft-cloud-pkiの制約","Microsoft Cloud PKIの制約",[253,295,296],{},"Microsoft Cloud PKIは、ADCSのような従来型のPKIをそのまま置き換えるものとしては設計されていません。足りない部分を埋めるために、2つ目のPKIが依然として必要になる組織も多くあります。",[298,299,300],"h3",{"id":300},"デバイスとプラットフォーム対応の限界",[278,302,303,306,309,312],{},[281,304,305],{},"Linuxシステムへのネイティブ対応がない",[281,307,308],{},"サーバーに非対応",[281,310,311],{},"IoTデバイスに非対応",[281,313,314],{},"ネットワークインフラ機器に非対応",[298,316,318],{"id":317},"active-directoryの自動登録に非対応","Active Directoryの自動登録に非対応",[278,320,321,324,327],{},[281,322,323],{},"ドメイン参加済みのWindows環境でADCSを置き換えられない",[281,325,326],{},"グループポリシーによる登録の仕組みが標準にない",[281,328,329],{},"サードパーティ製MDMのエコシステムに非対応",[298,331,333],{"id":332},"intuneへの強い依存","Intuneへの強い依存",[278,335,336],{},[281,337,338],{},"Jamf、Iru（旧Kandji）、Mosyle、Google Workspaceに対応しない",[298,340,341],{"id":341},"柔軟な証明書発行ができない",[278,343,344,347],{},[281,345,346],{},"APIと手動発行の機能が限定的",[281,348,349],{},"自動化を多用する環境には不向き",[263,351,353],{"id":352},"microsoft-cloud-pkiとscepman-enterprise-editionの比較","Microsoft Cloud PKIとSCEPman Enterprise Editionの比較",[253,355,356],{},[357,358,359],"em",{},"2026年5月時点で公開されている製品ドキュメントに基づく比較です。機能は変更される場合があります。",[361,362,364],"div",{"style":363},"grid-column: content; overflow-x: auto;",[365,366,367,368],"table",{},"\n  ",[369,370,371,367,386,367,397,367,407,367,416,367,425,367,434,367,443,367,452],"tbody",{},[372,373,374,375,374,380,374,383,367],"tr",{},"\n    ",[376,377,379],"th",{"style":378},"padding-right: 3rem;","機能",[376,381,382],{},"Microsoft Cloud PKI",[376,384,385],{},"SCEPman Enterprise Edition",[372,387,374,388,374,392,374,395,367],{},[389,390,391],"td",{"style":378},"Intuneで管理するデバイス",[389,393,394],{},"✓",[389,396,394],{},[372,398,374,399,374,402,374,405,367],{},[389,400,401],{"style":378},"Linuxデバイス",[389,403,404],{},"✗",[389,406,394],{},[372,408,374,409,374,412,374,414,367],{},[389,410,411],{"style":378},"Active Directoryの自動登録",[389,413,404],{},[389,415,394],{},[372,417,374,418,374,421,374,423,367],{},[389,419,420],{"style":378},"サーバー",[389,422,404],{},[389,424,394],{},[372,426,374,427,374,430,374,432,367],{},[389,428,429],{"style":378},"ネットワーク機器",[389,431,404],{},[389,433,394],{},[372,435,374,436,374,439,374,441,367],{},[389,437,438],{"style":378},"IoTデバイス",[389,440,404],{},[389,442,394],{},[372,444,374,445,374,448,374,450,367],{},[389,446,447],{"style":378},"手動およびAPIによる証明書発行",[389,449,404],{},[389,451,394],{},[372,453,374,454,374,457,374,459,367],{},[389,455,456],{"style":378},"サードパーティ製MDM（Jamf Pro、Google Workspace、Iru（旧Kandji）、Mosyle、SOTI MobiControlなど）",[389,458,404],{},[389,460,394],{},[263,462,464],{"id":463},"microsoft-cloud-pkiの代替が求められる理由","Microsoft Cloud PKIの代替が求められる理由",[253,466,467],{},"Microsoft Cloud PKIを検討する組織の多くは、次のいずれかの状況にあります。",[298,469,471],{"id":470},"_1adcsは今も必要だ","1.「ADCSは今も必要だ」",[253,473,474],{},"Intune向けにCloud PKIを導入しつつ、ドメイン参加済みのWindowsマシン、サーバー、社内サービスのためにADCSを稼働させ続けるケースです。その結果、PKIは1つではなく2つになり、習熟、管理、パッチ適用の対象も2系統に増えます。さらに、運用の複雑さからADCSを手放したいと考えていた組織も多いのですが、Microsoft Cloud PKIはその道筋を示してくれません。",[298,476,478],{"id":477},"_2intune管理外のデバイスがある","2.「Intune管理外のデバイスがある」",[253,480,481],{},"代表的な抜け漏れは、Linuxワークロード、ネットワークインフラ、Jamfで管理するApple環境です。Cloud PKIはこれらに対応しません。",[298,483,485],{"id":484},"_3自動化が必要だ","3.「自動化が必要だ」",[253,487,488],{},"最新の環境では、APIによる証明書発行、DevOpsワークフローへの組み込み、動的なインフラストラクチャーへの対応が求められます。Cloud PKIはこれを想定して作られていません。",[263,490,492],{"id":491},"microsoft-cloud-pkiの代替を選ぶ際の確認点","Microsoft Cloud PKIの代替を選ぶ際の確認点",[253,494,495],{},"現実的な置き換え先には、すべての証明書ユースケースを1つのシステムで扱えることが求められます。",[278,497,498,504,510,516,522],{},[281,499,500,503],{},[273,501,502],{},"デバイスの完全な網羅","：エンドポイント、サーバー、ネットワーク機器、IoTを1つのPKIで扱えます",[281,505,506,509],{},[273,507,508],{},"Active Directoryとの連携","：レガシーなADCSに頼らずに自動登録へ対応します",[281,511,512,515],{},[273,513,514],{},"複数MDMへの対応","：Intune、Jamf Pro、Google Workspace MDM、Iru（旧Kandji）、Mosyle、SOTI MobiControlなどにまたがって利用できます",[281,517,518,521],{},[273,519,520],{},"柔軟な証明書発行","：Intuneが制御基盤ではない場面でも、手動の運用とAPIによる発行に対応します",[281,523,524,527],{},[273,525,526],{},"Azureネイティブの展開","：オンプレミス基盤を追加することなく、自社のAzureテナント内で動作するクラウドベースのPKIです",[263,529,531],{"id":530},"scepmanがmicrosoft-cloud-pkiに加えて提供するもの","SCEPmanがMicrosoft Cloud PKIに加えて提供するもの",[253,533,534],{},"SCEPmanは、Microsoft Cloud PKIでは十分に扱えない証明書ユースケースのために作られています。",[278,536,537,544,550,556,562,567],{},[281,538,539],{},[540,541,543],"a",{"href":542},"microsoft-cloud-pki-server-certificates","サーバー向けの証明書",[281,545,546],{},[540,547,549],{"href":548},"microsoft-cloud-pki-linux-certificates","Linuxエンドポイント向けの証明書",[281,551,552],{},[540,553,555],{"href":554},"microsoft-cloud-pki-network-device-certificates","ネットワーク機器向けの証明書",[281,557,558],{},[540,559,561],{"href":560},"microsoft-cloud-pki-iot-certificates","IoTデバイス向けの証明書",[281,563,564],{},[540,565,447],{"href":566},"microsoft-cloud-pki-manually-issuing-certificates",[281,568,569,570,573,574,573,578,573,582,573,586,590],{},"サードパーティ製MDMプラットフォームへの対応（",[540,571,79],{"href":572},"/mdms/pki-certificate-management-jamf-pro-mdm","、",[540,575,577],{"href":576},"/mdms/pki-certificate-management-google-workspace-mdm","Google Workspace",[540,579,581],{"href":580},"/mdms/pki-certificate-management-kandji-mdm","Iru（旧Kandji）",[540,583,585],{"href":584},"/mdms/pki-certificate-management-mosyle-mdm","Mosyle",[540,587,589],{"href":588},"/mdms/pki-certificate-management-soti-mobicontrol-mdm","SOTI MobiControl","など）",[253,592,593],{},"Azureに標準化しつつ混在環境を運用するチームにとっては、証明書管理を分断された複数のシステムに分けることなく対応範囲を広げられる、ということを意味します。",[263,595,597],{"id":596},"microsoft-cloud-pkiが今も適している場面","Microsoft Cloud PKIが今も適している場面",[253,599,600],{},"Cloud PKIは次の場合には十分に機能します。",[278,602,603,606,609],{},[281,604,605],{},"デバイスをIntuneだけで管理している",[281,607,608],{},"Linuxやサーバーの証明書が不要である",[281,610,611],{},"ADCSを置き換えるのではなく、Microsoft Cloud PKIを追加で使う",[253,613,614],{},"実際には、多くの組織がADCSを置き換えるのではなく、Microsoft Cloud PKIを併用しています。つまり、別々の基盤、ポリシー、運用負荷を抱えた2つのPKIを並行して稼働させることになります。",[253,616,617],{},"両方の環境について保守、パッチ適用、監視、トラブルシューティングが必要になり、複雑さが増すとともに、構成のずれや対応漏れのリスクも高まります。",[253,619,620],{},"その範囲を超えると、多くのチームは機能を拡張するか、置き換えることになります。",[263,622,624],{"id":623},"_2026年にscepmanが有力なmicrosoft-cloud-pki代替である理由","2026年にSCEPmanが有力なMicrosoft Cloud PKI代替である理由",[253,626,627],{},"組織がMicrosoft Cloud PKIの代替を探し始めるのは、たいてい次のような抜け漏れに直面したときです。",[278,629,630,633,636,639],{},[281,631,632],{},"サーバー、Linux、ネットワーク機器、IoTに対応していない",[281,634,635],{},"サードパーティ製MDMプラットフォームに対応していない",[281,637,638],{},"ハイブリッド環境でADCSを置き換える道筋がない",[281,640,641],{},"手動やAPIによる証明書運用に対応していない",[253,643,644],{},"SCEPmanは、Intuneで管理するエンドポイントの先までPKIを広げることで、これらの抜け漏れを埋めます。",[278,646,647,650,653,656],{},[281,648,649],{},"Linux、サーバー、ネットワーク機器、IoT向けの証明書",[281,651,652],{},"Jamf Pro、Google Workspace、Iru（旧Kandji）、Mosyle、SOTI MobiControlなどへの対応",[281,654,655],{},"自動化を多用する環境に向けた、手動およびAPIによる証明書発行",[281,657,658],{},"ADCS型の運用を今も使うハイブリッド構成に向けたActive Directoryの自動登録",[253,660,661],{},"証明書管理を複数のシステムに分散させる代わりに、これらのユースケースを1つのPKIに集約できます。",[263,663,664],{"id":664},"まとめ",[253,666,667],{},"Microsoft Cloud PKIが解決するのは、Intuneで管理するデバイスへ証明書を発行するという1つの課題です。PKI全体を置き換えるものではありません。",[253,669,670],{},"サーバー、Linux、ネットワークインフラ、IoT、手動の証明書運用、複数のデバイス管理システムが環境に含まれる場合は、より広い範囲をカバーするソリューションが必要です。",[253,672,673],{},"SCEPmanは、Intune限定の制約なしにAzureベースのPKIを使いたいチームにとって、2026年で最も分かりやすいMicrosoft Cloud PKI代替の1つです。",[263,675,677],{"id":676},"scepmanをご自身でお試しください","SCEPmanをご自身でお試しください",[253,679,680],{},"30日間トライアルを開始して、複数のPKIを運用することなく、サーバー、Linux、ネットワーク機器、ハイブリッド環境にわたって証明書を扱う方法をご確認ください。",[682,683,684],"style",{},".trial-cta:hover { --cta-copy-color: white !important; }",[253,686,687],{},[540,688,697],{"role":689,"className":690,"dataText":695,"href":696,"target":119},"button",[691,692,693,694],"cta","btn","btn-primary","trial-cta","SCEPmanの30日間トライアルを開始","https://support.scepman.com/support/tickets/new?ticket_form=trial_request_%28scepman%29",[698,699,695],"span",{"className":700},[701],"cta__text",[263,703,705],{"id":704},"microsoft-cloud-pkiに関するよくあるご質問","Microsoft Cloud PKIに関するよくあるご質問",[298,707,709],{"id":708},"microsoft-cloud-pkiの最適な代替は何ですか","Microsoft Cloud PKIの最適な代替は何ですか",[253,711,712,713,573,715,573,718,573,720,573,723,726],{},"SCEPmanは、混在環境を運用するチームにとって最も有力なMicrosoft Cloud PKI代替の1つです。Cloud PKIが扱わないユースケース、すなわち",[540,714,420],{"href":542},[540,716,717],{"href":548},"Linuxエンドポイント",[540,719,429],{"href":554},[540,721,722],{"href":560},"IoT",[540,724,725],{"href":566},"手動での証明書発行","、サードパーティ製MDMまでを、1つのAzureネイティブなPKIでカバーします。",[298,728,730],{"id":729},"microsoft-cloud-pkiはadcsの置き換えになりますか","Microsoft Cloud PKIはADCSの置き換えになりますか",[253,732,733],{},"いいえ。Active Directoryの自動登録や多くのサーバーのユースケースに対応していません。ほとんどの組織は、併せてADCSを残しています。",[298,735,737],{"id":736},"microsoft-cloud-pkiはlinuxに対応していますか","Microsoft Cloud PKIはLinuxに対応していますか",[253,739,740],{},"いいえ。Intuneは、Linuxシステムへの証明書発行に対応していません。",[298,742,744],{"id":743},"microsoft-cloud-pkiでネットワーク機器の証明書を発行できますか","Microsoft Cloud PKIでネットワーク機器の証明書を発行できますか",[253,746,747],{},"いいえ。主にIntuneで管理するエンドポイントを想定して設計されています。",[298,749,751],{"id":750},"microsoft-cloud-pkiはjamfやgoogle-workspaceと併用できますか","Microsoft Cloud PKIはJamfやGoogle Workspaceと併用できますか",[253,753,754],{},"いいえ。Intuneと密接に統合されています。",[298,756,758],{"id":757},"microsoft-cloud-pkiの主な制約は何ですか","Microsoft Cloud PKIの主な制約は何ですか",[253,760,761],{},"証明書のユースケースの一部、主にIntuneで管理するデバイスしかカバーしません。",{"title":763,"searchDepth":764,"depth":764,"links":765},"",2,[766,767,774,775,780,781,782,783,784,785,786],{"id":265,"depth":764,"text":266},{"id":292,"depth":764,"text":293,"children":768},[769,771,772,773],{"id":300,"depth":770,"text":300},3,{"id":317,"depth":770,"text":318},{"id":332,"depth":770,"text":333},{"id":341,"depth":770,"text":341},{"id":352,"depth":764,"text":353},{"id":463,"depth":764,"text":464,"children":776},[777,778,779],{"id":470,"depth":770,"text":471},{"id":477,"depth":770,"text":478},{"id":484,"depth":770,"text":485},{"id":491,"depth":764,"text":492},{"id":530,"depth":764,"text":531},{"id":596,"depth":764,"text":597},{"id":623,"depth":764,"text":624},{"id":664,"depth":764,"text":664},{"id":676,"depth":764,"text":677},{"id":704,"depth":764,"text":705,"children":787},[788,789,790,791,792,793],{"id":708,"depth":770,"text":709},{"id":729,"depth":770,"text":730},{"id":736,"depth":770,"text":737},{"id":743,"depth":770,"text":744},{"id":750,"depth":770,"text":751},{"id":757,"depth":770,"text":758},null,"md",false,"post",{"lang":799,"seoTitle":246,"titleClass":800,"date":801,"categories":802,"blogtitlepic":803,"socialimg":804,"customExcerpt":805,"keywords":806,"asideNav":807,"maxContent":831,"footer":832},"ja","h2-font-size","2026-05-01",[13],"header-scepman-cloud-pki-alternatives.png","/blog/heads/header-scepman-cloud-pki-alternatives.png","Microsoft Cloud PKIの代替をお探しですか。Cloud PKIが対象とするのはIntuneで管理するデバイスだけで、Linux、サーバー、IoTには対応しません。どこに限界があるのか、置き換え先を選ぶ際に何を確認すべきかをまとめました。","Microsoft Cloud PKI 代替, Microsoft Cloud PKIの代替, Microsoft Cloud PKI 置き換え, クラウドPKI 代替, Microsoft Intune PKI, SCEPman, ADCS, Active Directory",{"menuItems":808},[809,811,814,817,820,823,826,828],{"href":810,"text":266},"#microsoft-cloud-pkiとは",{"href":812,"text":813},"#microsoft-cloud-pkiの制約","制約",{"href":815,"text":816},"#microsoft-cloud-pkiとscepman-enterprise-editionの比較","Cloud PKIとSCEPmanの比較",{"href":818,"text":819},"#microsoft-cloud-pkiの代替が求められる理由","代替が求められる理由",{"href":821,"text":822},"#microsoft-cloud-pkiの代替を選ぶ際の確認点","選ぶ際の確認点",{"href":824,"text":825},"#microsoft-cloud-pkiが今も適している場面","Cloud PKIが適している場面",{"href":827,"text":664},"#まとめ",{"href":829,"text":830},"#microsoft-cloud-pkiに関するよくあるご質問","よくあるご質問",true,{"noMargin":831},"/posts/microsoft-cloud-pki-alternatives",{"title":246,"description":255},"posts/microsoft-cloud-pki-alternatives",[382,837,72,838],"Alternatives","PKI","-Ke_nms-zySIvvyaY0ISlUhEGeTph_OxNb_LSfprAKc",{"id":841,"extension":842,"meta":843,"stem":922,"__hash__":923},"authors_data/authors.json","json",{"path":844,"Alexander Rudolph":845,"Sophie Luna":851,"Nadine Kern":857,"Thorben Pöschus":863,"Karsten Kleinschmidt":869,"Julian Wendt":875,"Holger Bunkradt":880,"Ralf Mania":886,"Oliver Kieselbach":892,"Steffen Schwerdtfeger":898,"Christoph Hannebauer":904,"body":909,"title":921},"/authors",{"display_name":846,"avatar":847,"permalink":848,"twitter":849,"linkedin":850},"Alexander Rudolph","people/people-alexander-rudolph.png","author/alexander-rudolph/","AlexanderOnIT","rudolph-alexander",{"display_name":852,"avatar":853,"permalink":854,"twitter":855,"linkedin":856},"Sophie Luna","c_thumb,h_1600,w_1600/people/people-sophie-luna.jpg","author/sophie-luna/","glueckkanjagab","company/glueckkanja-gab",{"display_name":858,"avatar":859,"permalink":860,"twitter":861,"linkedin":862},"Nadine Kern","people/people-nadine-kern.png","author/nadine-kern/","nadineausRT","nadine-kern",{"display_name":864,"avatar":865,"permalink":866,"twitter":867,"linkedin":868},"Thorben Pöschus","people/people-thorben-poeschus.png","author/thorben-poeschus/","TPO901","thorben-pöschus-624693b7",{"display_name":870,"avatar":871,"permalink":872,"twitter":873,"linkedin":874},"Karsten Kleinschmidt","people/people-karsten-kleinschmidt.png","author/karsten-kleinschmidt/","KarstenonIT","karstenkleinschmidt",{"display_name":876,"avatar":877,"permalink":878,"linkedin":879},"Julian Wendt","people/people-julian-wendt.png","author/julian-wendt/","julian-wendt",{"display_name":881,"avatar":882,"permalink":883,"linkedin":884,"twitter":885},"Holger Bunkradt","people/people-holger-bunkradt.png","author/holger-bunkradt/","holger-bunkradt-12b5053b","hbunkradt",{"display_name":887,"avatar":888,"permalink":889,"linkedin":890,"twitter":891},"Ralf Mania","people/people-ralf-mania.png","author/ralf-mania/","ralf-mania-146a2757","RaMa1976",{"display_name":893,"avatar":894,"permalink":895,"linkedin":896,"twitter":897},"Oliver Kieselbach","people/people-oliver-kieselbach.png","author/oliver-kieselbach/","oliver-kieselbach-a4a3409","okieselbT",{"display_name":899,"avatar":900,"permalink":901,"linkedin":902,"twitter":903},"Steffen Schwerdtfeger","people/people-steffen-schwerdtfeger.png","author/steffen-schwerdtfeger/","steffen-schwerdtfeger","SteffenAtCloud",{"display_name":905,"avatar":906,"permalink":907,"twitter":855,"linkedin":856,"imageOffsetTop":908},"Dr. Christoph Hannebauer","people/people-christoph-hannebauer.png","/authors/christoph-hannebauer/","72%",{"Alexander Rudolph":910,"Sophie Luna":911,"Nadine Kern":912,"Thorben Pöschus":913,"Karsten Kleinschmidt":914,"Julian Wendt":915,"Holger Bunkradt":916,"Ralf Mania":917,"Oliver Kieselbach":918,"Steffen Schwerdtfeger":919,"Christoph Hannebauer":920},{"display_name":846,"avatar":847,"permalink":848,"twitter":849,"linkedin":850},{"display_name":852,"avatar":853,"permalink":854,"twitter":855,"linkedin":856},{"display_name":858,"avatar":859,"permalink":860,"twitter":861,"linkedin":862},{"display_name":864,"avatar":865,"permalink":866,"twitter":867,"linkedin":868},{"display_name":870,"avatar":871,"permalink":872,"twitter":873,"linkedin":874},{"display_name":876,"avatar":877,"permalink":878,"linkedin":879},{"display_name":881,"avatar":882,"permalink":883,"linkedin":884,"twitter":885},{"display_name":887,"avatar":888,"permalink":889,"linkedin":890,"twitter":891},{"display_name":893,"avatar":894,"permalink":895,"linkedin":896,"twitter":897},{"display_name":899,"avatar":900,"permalink":901,"linkedin":902,"twitter":903},{"display_name":905,"avatar":906,"permalink":907,"twitter":855,"linkedin":856,"imageOffsetTop":908},"Authors","authors","PIJJchcHqfzD5YPmn4V8YLxY6gtySOfBG5u8lTczi2w",{"id":841,"extension":842,"meta":925,"stem":922,"__hash__":923},{},{"list":927,"authors":1047},[928,949,967,981,986,999,1011,1023,1035],{"id":929,"title":930,"author":931,"cta":794,"description":763,"hideInRecent":796,"layout":797,"meta":932,"moment":933,"path":937,"stem":938,"tags":939,"webcast":796},"content_ja/posts/kb5127648-peap-mschapv2-eap-tls.md","KB5127648とNTLMv1：PEAP-MSCHAPv2 Wi-Fi・LAN・VPNが接続できなくなった理由と恒久的な解決策",[248],{"lang":799,"date":933,"categories":934,"blogtitlepic":935,"customExcerpt":936},"2026-10-16",[13],"header-scepman-KB5127648.png","KB5127648はデフォルトでNTLMv1 SSOをブロックします。PEAP-MSCHAPv2 Wi-Fi・LAN・VPNが接続できなくなる理由、BlockNtlmv1SSO回避策、そして恒久的な解決策であるEAP-TLSについて解説します。","/posts/kb5127648-peap-mschapv2-eap-tls","posts/kb5127648-peap-mschapv2-eap-tls",[940,941,942,943,944,945,946,947,948],"KB5127648","NTLMv1","MS-CHAPv2","PEAP","EAP-TLS","Credential Guard","802.1X","Intune","RADIUS",{"id":950,"title":951,"author":952,"cta":794,"description":954,"hideInRecent":796,"layout":797,"meta":955,"moment":956,"path":960,"stem":961,"tags":962,"webcast":796},"content_ja/posts/private-ca-vs-public-ca.md","プライベートCAとパブリックCA：選び方を間違えているかもしれません",[953],"Kevin Vo","余裕のないIT部門にとって、パブリックな認証局（CA）は万能のハンマーのように見え、暗号化の要件はすべて釘のように見えてきます。しかし、あらゆる用途にパブリックCAを使うことは、本番環境を静かに壊す最もよくある原因の1つです。",{"lang":799,"date":956,"categories":957,"blogtitlepic":958,"customExcerpt":959},"2026-08-24",[13],"header-scepman-private-vs-public-ca.png","パブリックCAの証明書は、2027年3月までにクライアント認証への対応を失います。プライベートCAが必要になる場面と、SCEPmanが発行を自動化する仕組みをご紹介します。","/posts/private-ca-vs-public-ca","posts/private-ca-vs-public-ca",[963,964,838,965,966],"Private CA","Public CA","Client Authentication","Certificate Authority",{"id":968,"title":969,"author":970,"cta":794,"description":971,"hideInRecent":796,"layout":797,"meta":972,"moment":801,"path":976,"stem":977,"tags":978,"webcast":796},"content_ja/posts/adcs-alternatives.md","2026年のMicrosoft ADCS代替ソリューション",[248],"Microsoft Active Directory Certificate Servicesは、ADCS、ADCA、Microsoft CAとも呼ばれ、長年にわたりWindows環境の標準的な公開鍵基盤（PKI）として使われてきました。今も多くの組織が、ユーザー、デバイス、サーバーへの証明書発行をこの仕組みに頼っています。",{"lang":799,"date":801,"categories":973,"blogtitlepic":974,"customExcerpt":975},[13],"header-scepman-adcs-alternatives.png","ADCS、ADCA、Microsoft CAの代替をお探しですか。Active Directory Certificate Servicesは、最新の環境には不要な複雑さを持ち込みます。置き換え先を選ぶ際に確認すべき点をまとめました。","/posts/adcs-alternatives","posts/adcs-alternatives",[979,837,838,980],"ADCS","Active Directory Certificate Services",{"id":245,"title":246,"author":982,"cta":794,"description":255,"hideInRecent":796,"layout":797,"meta":983,"moment":801,"path":833,"stem":835,"tags":985,"webcast":796},[248],{"lang":799,"date":801,"categories":984,"blogtitlepic":803,"customExcerpt":805},[13],[382,837,72,838],{"id":987,"title":988,"author":989,"cta":794,"description":763,"hideInRecent":796,"layout":797,"meta":990,"moment":991,"path":995,"stem":996,"tags":997,"webcast":796},"content_ja/posts/microsoft-cloud-pki-iot-certificates.md","Microsoft Cloud PKIでのIoT証明書の作成：代替手段と解決策",[248],{"lang":799,"date":991,"categories":992,"blogtitlepic":993,"customExcerpt":994},"2026-03-25",[13],"header-scepman-iot-certificates.png","Microsoft Cloud PKIでIoTデバイスの証明書を作成し管理する方法をお探しですか。残念ながら、Microsoft Cloud PKIはIoT証明書に対応していません。設計上、対象はIntuneで管理するデバイスに限られます。","/posts/microsoft-cloud-pki-iot-certificates","posts/microsoft-cloud-pki-iot-certificates",[382,998,72],"IoT Certificates",{"id":1000,"title":1001,"author":1002,"cta":794,"description":763,"hideInRecent":796,"layout":797,"meta":1003,"moment":991,"path":1007,"stem":1008,"tags":1009,"webcast":796},"content_ja/posts/microsoft-cloud-pki-linux-certificates.md","Microsoft Cloud PKIでのLinuxエンドポイント証明書の作成：代替手段と解決策",[248],{"lang":799,"date":991,"categories":1004,"blogtitlepic":1005,"customExcerpt":1006},[13],"header-scepman-linux-endpoint-certificates.png","Microsoft Cloud PKIでLinuxエンドポイントの証明書を作成し管理する手段をお探しですか。残念ながら、Microsoft Cloud PKIはLinuxエンドポイントの証明書に対応していません。","/posts/microsoft-cloud-pki-linux-certificates","posts/microsoft-cloud-pki-linux-certificates",[382,1010,72],"Linux Endpoint Certificates",{"id":1012,"title":1013,"author":1014,"cta":794,"description":763,"hideInRecent":796,"layout":797,"meta":1015,"moment":991,"path":1019,"stem":1020,"tags":1021,"webcast":796},"content_ja/posts/microsoft-cloud-pki-manually-issuing-certificates.md","Microsoft Cloud PKIでの証明書の手動発行：代替手段と解決策",[248],{"lang":799,"date":991,"categories":1016,"blogtitlepic":1017,"customExcerpt":1018},[13],"header-scepman-manual-certificates.png","Webサーバーの保護やコード署名など、特定の場面で証明書を手動で発行する必要がありますか。残念ながら、Microsoft Cloud PKIは証明書の手動発行に対応していません。設計上、対象はIntuneで管理するデバイスに限られます。","/posts/microsoft-cloud-pki-manually-issuing-certificates","posts/microsoft-cloud-pki-manually-issuing-certificates",[382,1022,72],"Manually Issued Certificates",{"id":1024,"title":1025,"author":1026,"cta":794,"description":763,"hideInRecent":796,"layout":797,"meta":1027,"moment":991,"path":1031,"stem":1032,"tags":1033,"webcast":796},"content_ja/posts/microsoft-cloud-pki-network-device-certificates.md","Microsoft Cloud PKIでのネットワーク機器向け証明書の作成：代替手段と解決策",[248],{"lang":799,"date":991,"categories":1028,"blogtitlepic":1029,"customExcerpt":1030},[13],"header-scepman-certificates-network-devices.png","Microsoft Cloud PKIでネットワーク機器の証明書を作成し管理する手段をお探しですか。残念ながら、Microsoft Cloud PKIはネットワーク機器の証明書に対応していません。設計上、対象はIntuneで管理するデバイスに限られます。","/posts/microsoft-cloud-pki-network-device-certificates","posts/microsoft-cloud-pki-network-device-certificates",[382,1034,72],"Network Device Certificates",{"id":1036,"title":1037,"author":1038,"cta":794,"description":763,"hideInRecent":796,"layout":797,"meta":1039,"moment":991,"path":1043,"stem":1044,"tags":1045,"webcast":796},"content_ja/posts/microsoft-cloud-pki-server-certificates.md","Microsoft Cloud PKIでのサーバー証明書の作成：代替手段と解決策",[248],{"lang":799,"date":991,"categories":1040,"blogtitlepic":1041,"customExcerpt":1042},[13],"header-scepman-server-certificates.png","Microsoft Cloud PKIでサーバー証明書を作成する方法をお探しですか。多くの組織が証明書管理にMicrosoftのPKIソリューションを利用していますが、大きな制約があります。Microsoft Cloud PKIはサーバー証明書に対応していません。設計上、対象はIntuneで管理するデバイスに限られます。","/posts/microsoft-cloud-pki-server-certificates","posts/microsoft-cloud-pki-server-certificates",[382,1046,72],"Server Certificates",{},1794857538000]