DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get solution/microsoft -o yaml$ soultec get solution/microsoft -o json$ soultec get solution/microsoft -o toml$ soultec get solution/microsoft -o xml$ python3 microsoft.pyPS> ./microsoft.ps1$ go run microsoft.go$ node microsoft.js

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: microsoft locale: en labels: vendor: Microsoft capability/cloud: 1.92 capability/modern-workplace: 1.69 capability/security: 1.91 vendor/microsoft: 2.61 annotations: source: src/content/solutions/en/microsoft.md route: /en/solutions/microsoft/ schema: /nerd/schema/solutions.json markdown: /en/solutions/microsoft.mdspec: title: Microsoft tags: [cloud, modern-workplace, security] vendors: [microsoft] summary: >- From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity. photoNeed: >- An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented stub: false draft: false kind: vendor addon: false vendorName: Microsoft status: current featuredExperts: [mike-schmid, matthias-frech] sections: - heading:

What we do

body: | **Planning and design.** Choosing the services you actually need, and Microsoft 365 security workshops so the configuration stays sound. **Introduction.** From the first concept through a proof of concept to a phased rollout. Phased, because a migration done in one go fails on the exceptions. **Setup and configuration.** The technical side of each service, and the policies behind them. **Operation.** When something sticks later on, we answer. - heading:

Where it actually gets difficult

body: | Our work usually starts with Exchange Online and continues with Entra ID. The mailbox migration is manageable. Conditional access, guest accounts and the question of who is really a Global Administrator take considerably longer. The second recurring item is storage. It moves from a file server with permissions that grew over time into SharePoint, and the permissions move with it. They are best cleaned up during the migration.status: corpus: 315 services: - {ref: services/modern-workplace, score: 0.61} - {ref: services/cloud, score: 0.53} - {ref: services/digital-workplace, score: 0.44} - {ref: services/orchestration-automation, score: 0.43} experts: - {ref: experts/mike-schmid, score: 0.41, featured: true} - {ref: experts/matthias-frech, score: 0.48, featured: true} - {ref: experts/oliver-erismann, score: 0.47} neighbours: - {ref: solutions/microsoft/microsoft-azure, score: 1.00} - {ref: solutions/microsoft/microsoft-365, score: 0.76} - {ref: solutions/microsoft/microsoft-teams, score: 0.51} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "microsoft", "locale": "en", "labels": { "vendor": "Microsoft", "capability/cloud": 1.92, "capability/modern-workplace": 1.69, "capability/security": 1.91, "vendor/microsoft": 2.61 }, "annotations": { "source": "src/content/solutions/en/microsoft.md", "route": "/en/solutions/microsoft/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/microsoft.md" } }, "spec": { "title": "Microsoft", "tags": [ "cloud", "modern-workplace", "security" ], "vendors": [ "microsoft" ], "summary": "From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.", "photoNeed": "An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented", "stub": false, "draft": false, "kind": "vendor", "addon": false, "vendorName": "Microsoft", "status": "current", "featuredExperts": [ "mike-schmid", "matthias-frech" ], "sections": [ { "heading": "

What we do

", "body": "**Planning and design.** Choosing the services you actually need, and Microsoft 365\nsecurity workshops so the configuration stays sound.\n\n**Introduction.** From the first concept through a proof of concept to a phased rollout.\nPhased, because a migration done in one go fails on the exceptions.\n\n**Setup and configuration.** The technical side of each service, and the policies behind\nthem.\n\n**Operation.** When something sticks later on, we answer." }, { "heading": "

Where it actually gets difficult

", "body": "Our work usually starts with Exchange Online and continues with Entra ID. The mailbox\nmigration is manageable. Conditional access, guest accounts and the question of who is\nreally a Global Administrator take considerably longer.\n\nThe second recurring item is storage. It moves from a file server with permissions that\ngrew over time into SharePoint, and the permissions move with it. They are best cleaned up\nduring the migration." } ] }, "status": { "corpus": 315, "services": [ { "ref": "services/modern-workplace", "score": "0.61" }, { "ref": "services/cloud", "score": "0.53" }, { "ref": "services/digital-workplace", "score": "0.44" }, { "ref": "services/orchestration-automation", "score": "0.43" } ], "experts": [ { "ref": "experts/mike-schmid", "score": "0.41", "featured": true }, { "ref": "experts/matthias-frech", "score": "0.48", "featured": true }, { "ref": "experts/oliver-erismann", "score": "0.47" } ], "neighbours": [ { "ref": "solutions/microsoft/microsoft-azure", "score": "1.00" }, { "ref": "solutions/microsoft/microsoft-365", "score": "0.76" }, { "ref": "solutions/microsoft/microsoft-teams", "score": "0.51" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "microsoft"locale = "en"[metadata.labels]vendor = "Microsoft""capability/cloud" = 1.92"capability/modern-workplace" = 1.69"capability/security" = 1.91"vendor/microsoft" = 2.61[metadata.annotations]source = "src/content/solutions/en/microsoft.md"route = "/en/solutions/microsoft/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/microsoft.md"[spec]title = "Microsoft"tags = ["cloud", "modern-workplace", "security"]vendors = ["microsoft"]summary = "From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity."photoNeed = "An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented"stub = falsedraft = falsekind = "vendor"addon = falsevendorName = "Microsoft"status = "current"featuredExperts = ["mike-schmid", "matthias-frech"][[spec.sections]]heading = "

What we do

"body = '''**Planning and design.** Choosing the services you actually need, and Microsoft 365security workshops so the configuration stays sound.**Introduction.** From the first concept through a proof of concept to a phased rollout.Phased, because a migration done in one go fails on the exceptions.**Setup and configuration.** The technical side of each service, and the policies behindthem.**Operation.** When something sticks later on, we answer.'''[[spec.sections]]heading = "

Where it actually gets difficult

"body = '''Our work usually starts with Exchange Online and continues with Entra ID. The mailboxmigration is manageable. Conditional access, guest accounts and the question of who isreally a Global Administrator take considerably longer.The second recurring item is storage. It moves from a file server with permissions thatgrew over time into SharePoint, and the permissions move with it. They are best cleaned upduring the migration.'''[status]corpus = 315search = "/en/search.json"[[status.services]]ref = "services/modern-workplace"score = "0.61"[[status.services]]ref = "services/cloud"score = "0.53"[[status.services]]ref = "services/digital-workplace"score = "0.44"[[status.services]]ref = "services/orchestration-automation"score = "0.43"[[status.experts]]ref = "experts/mike-schmid"score = "0.41"featured = true[[status.experts]]ref = "experts/matthias-frech"score = "0.48"featured = true[[status.experts]]ref = "experts/oliver-erismann"score = "0.47"[[status.neighbours]]ref = "solutions/microsoft/microsoft-azure"score = "1.00"[[status.neighbours]]ref = "solutions/microsoft/microsoft-365"score = "0.76"[[status.neighbours]]ref = "solutions/microsoft/microsoft-teams"score = "0.51"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>microsoft</name> <locale>en</locale> <labels> <vendor>Microsoft</vendor> <entry key="capability/cloud">1.92</entry> <entry key="capability/modern-workplace">1.69</entry> <entry key="capability/security">1.91</entry> <entry key="vendor/microsoft">2.61</entry> </labels> <annotations> <source>src/content/solutions/en/microsoft.md</source> <route>/en/solutions/microsoft/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/microsoft.md</markdown> </annotations> </metadata> <spec> <title>Microsoft</title> <tags> <item>cloud</item> <item>modern-workplace</item> <item>security</item> </tags> <vendors> <item>microsoft</item> </vendors> <summary>From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.</summary> <photoNeed>An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented</photoNeed> <stub>false</stub> <draft>false</draft> <kind>vendor</kind> <addon>false</addon> <vendorName>Microsoft</vendorName> <status>current</status> <featuredExperts> <item>mike-schmid</item> <item>matthias-frech</item> </featuredExperts> <sections> <section> <heading>

What we do

</heading> <body>**Planning and design.** Choosing the services you actually need, and Microsoft 365security workshops so the configuration stays sound.**Introduction.** From the first concept through a proof of concept to a phased rollout.Phased, because a migration done in one go fails on the exceptions.**Setup and configuration.** The technical side of each service, and the policies behindthem.**Operation.** When something sticks later on, we answer. </body> </section> <section> <heading>

Where it actually gets difficult

</heading> <body>Our work usually starts with Exchange Online and continues with Entra ID. The mailboxmigration is manageable. Conditional access, guest accounts and the question of who isreally a Global Administrator take considerably longer.The second recurring item is storage. It moves from a file server with permissions thatgrew over time into SharePoint, and the permissions move with it. They are best cleaned upduring the migration. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <services> <item> <ref>services/modern-workplace</ref> <score>0.61</score> </item> <item> <ref>services/cloud</ref> <score>0.53</score> </item> <item> <ref>services/digital-workplace</ref> <score>0.44</score> </item> <item> <ref>services/orchestration-automation</ref> <score>0.43</score> </item> </services> <experts> <item> <ref>experts/mike-schmid</ref> <score>0.41</score> <featured>true</featured> </item> <item> <ref>experts/matthias-frech</ref> <score>0.48</score> <featured>true</featured> </item> <item> <ref>experts/oliver-erismann</ref> <score>0.47</score> </item> </experts> <neighbours> <item> <ref>solutions/microsoft/microsoft-azure</ref> <score>1.00</score> </item> <item> <ref>solutions/microsoft/microsoft-365</ref> <score>0.76</score> </item> <item> <ref>solutions/microsoft/microsoft-teams</ref> <score>0.51</score> </item> </neighbours> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "microsoft", "locale": "en", "labels": { "vendor": "Microsoft", "capability/cloud": 1.92, "capability/modern-workplace": 1.69, "capability/security": 1.91, "vendor/microsoft": 2.61, }, "annotations": { "source": "src/content/solutions/en/microsoft.md", "route": "/en/solutions/microsoft/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/microsoft.md", }, }, "spec": { "title": "Microsoft", "tags": ["cloud", "modern-workplace", "security"], "vendors": ["microsoft"], "summary": "From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.", "photoNeed": "An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented", "stub": False, "draft": False, "kind": "vendor", "addon": False, "vendorName": "Microsoft", "status": "current", "featuredExperts": ["mike-schmid", "matthias-frech"], "sections": [ { "heading": "

What we do

", "body": ( "**Planning and design.** Choosing the services you actually need, and Microsoft 365\n" "security workshops so the configuration stays sound.\n" "\n" "**Introduction.** From the first concept through a proof of concept to a phased rollout.\n" "Phased, because a migration done in one go fails on the exceptions.\n" "\n" "**Setup and configuration.** The technical side of each service, and the policies behind\n" "them.\n" "\n" "**Operation.** When something sticks later on, we answer." ), }, { "heading": "

Where it actually gets difficult

", "body": ( "Our work usually starts with Exchange Online and continues with Entra ID. The mailbox\n" "migration is manageable. Conditional access, guest accounts and the question of who is\n" "really a Global Administrator take considerably longer.\n" "\n" "The second recurring item is storage. It moves from a file server with permissions that\n" "grew over time into SharePoint, and the permissions move with it. They are best cleaned up\n" "during the migration." ), }, ], }, "status": { "corpus": 315, "services": [ { "ref": "services/modern-workplace", "score": "0.61", }, { "ref": "services/cloud", "score": "0.53", }, { "ref": "services/digital-workplace", "score": "0.44", }, { "ref": "services/orchestration-automation", "score": "0.43", }, ], "experts": [ { "ref": "experts/mike-schmid", "score": "0.41", "featured": True, }, { "ref": "experts/matthias-frech", "score": "0.48", "featured": True, }, { "ref": "experts/oliver-erismann", "score": "0.47", }, ], "neighbours": [ { "ref": "solutions/microsoft/microsoft-azure", "score": "1.00", }, { "ref": "solutions/microsoft/microsoft-365", "score": "0.76", }, { "ref": "solutions/microsoft/microsoft-teams", "score": "0.51", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Solution' metadata = [ordered]@{ name = 'microsoft' locale = 'en' labels = [ordered]@{ vendor = 'Microsoft' 'capability/cloud' = 1.92 'capability/modern-workplace' = 1.69 'capability/security' = 1.91 'vendor/microsoft' = 2.61 } annotations = [ordered]@{ source = 'src/content/solutions/en/microsoft.md' route = '/en/solutions/microsoft/' schema = '/nerd/schema/solutions.json' markdown = '/en/solutions/microsoft.md' } } spec = [ordered]@{ title = 'Microsoft' tags = @('cloud', 'modern-workplace', 'security') vendors = @('microsoft') summary = 'From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.' photoNeed = 'An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented' stub = $false draft = $false kind = 'vendor' addon = $false vendorName = 'Microsoft' status = 'current' featuredExperts = @('mike-schmid', 'matthias-frech') sections = @( [ordered]@{ heading = '

What we do

' body = @'**Planning and design.** Choosing the services you actually need, and Microsoft 365security workshops so the configuration stays sound.**Introduction.** From the first concept through a proof of concept to a phased rollout.Phased, because a migration done in one go fails on the exceptions.**Setup and configuration.** The technical side of each service, and the policies behindthem.**Operation.** When something sticks later on, we answer.'@ } [ordered]@{ heading = '

Where it actually gets difficult

' body = @'Our work usually starts with Exchange Online and continues with Entra ID. The mailboxmigration is manageable. Conditional access, guest accounts and the question of who isreally a Global Administrator take considerably longer.The second recurring item is storage. It moves from a file server with permissions thatgrew over time into SharePoint, and the permissions move with it. They are best cleaned upduring the migration.'@ } ) } status = [ordered]@{ corpus = 315 services = @( [ordered]@{ ref = 'services/modern-workplace' score = '0.61' } [ordered]@{ ref = 'services/cloud' score = '0.53' } [ordered]@{ ref = 'services/digital-workplace' score = '0.44' } [ordered]@{ ref = 'services/orchestration-automation' score = '0.43' } ) experts = @( [ordered]@{ ref = 'experts/mike-schmid' score = '0.41' featured = $true } [ordered]@{ ref = 'experts/matthias-frech' score = '0.48' featured = $true } [ordered]@{ ref = 'experts/oliver-erismann' score = '0.47' } ) neighbours = @( [ordered]@{ ref = 'solutions/microsoft/microsoft-azure' score = '1.00' } [ordered]@{ ref = 'solutions/microsoft/microsoft-365' score = '0.76' } [ordered]@{ ref = 'solutions/microsoft/microsoft-teams' score = '0.51' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": map[string]any{ "name": "microsoft", "locale": "en", "labels": map[string]any{ "vendor": "Microsoft", "capability/cloud": 1.92, "capability/modern-workplace": 1.69, "capability/security": 1.91, "vendor/microsoft": 2.61, }, "annotations": map[string]any{ "source": "src/content/solutions/en/microsoft.md", "route": "/en/solutions/microsoft/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/microsoft.md", }, }, "spec": map[string]any{ "title": "Microsoft", "tags": []any{"cloud", "modern-workplace", "security"}, "vendors": []any{"microsoft"}, "summary": "From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.", "photoNeed": "An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented", "stub": false, "draft": false, "kind": "vendor", "addon": false, "vendorName": "Microsoft", "status": "current", "featuredExperts": []any{"mike-schmid", "matthias-frech"}, "sections": []any{ map[string]any{ "heading": "

What we do

", "body": "**Planning and design.** Choosing the services you actually need, and Microsoft 365\n" + "security workshops so the configuration stays sound.\n" + "\n" + "**Introduction.** From the first concept through a proof of concept to a phased rollout.\n" + "Phased, because a migration done in one go fails on the exceptions.\n" + "\n" + "**Setup and configuration.** The technical side of each service, and the policies behind\n" + "them.\n" + "\n" + "**Operation.** When something sticks later on, we answer.", }, map[string]any{ "heading": "

Where it actually gets difficult

", "body": "Our work usually starts with Exchange Online and continues with Entra ID. The mailbox\n" + "migration is manageable. Conditional access, guest accounts and the question of who is\n" + "really a Global Administrator take considerably longer.\n" + "\n" + "The second recurring item is storage. It moves from a file server with permissions that\n" + "grew over time into SharePoint, and the permissions move with it. They are best cleaned up\n" + "during the migration.", }, }, }, "status": map[string]any{ "corpus": 315, "services": []any{ map[string]any{ "ref": "services/modern-workplace", "score": "0.61", }, map[string]any{ "ref": "services/cloud", "score": "0.53", }, map[string]any{ "ref": "services/digital-workplace", "score": "0.44", }, map[string]any{ "ref": "services/orchestration-automation", "score": "0.43", }, }, "experts": []any{ map[string]any{ "ref": "experts/mike-schmid", "score": "0.41", "featured": true, }, map[string]any{ "ref": "experts/matthias-frech", "score": "0.48", "featured": true, }, map[string]any{ "ref": "experts/oliver-erismann", "score": "0.47", }, }, "neighbours": []any{ map[string]any{ "ref": "solutions/microsoft/microsoft-azure", "score": "1.00", }, map[string]any{ "ref": "solutions/microsoft/microsoft-365", "score": "0.76", }, map[string]any{ "ref": "solutions/microsoft/microsoft-teams", "score": "0.51", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Solution", metadata: { name: "microsoft", locale: "en", labels: { vendor: "Microsoft", "capability/cloud": 1.92, "capability/modern-workplace": 1.69, "capability/security": 1.91, "vendor/microsoft": 2.61, }, annotations: { source: "src/content/solutions/en/microsoft.md", route: "/en/solutions/microsoft/", schema: "/nerd/schema/solutions.json", markdown: "/en/solutions/microsoft.md", }, }, spec: { title: "Microsoft", tags: ["cloud", "modern-workplace", "security"], vendors: ["microsoft"], summary: "From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.", photoNeed: "An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented", stub: false, draft: false, kind: "vendor", addon: false, vendorName: "Microsoft", status: "current", featuredExperts: ["mike-schmid", "matthias-frech"], sections: [ { heading: "

What we do

", body: "**Planning and design.** Choosing the services you actually need, and Microsoft 365\n" + "security workshops so the configuration stays sound.\n" + "\n" + "**Introduction.** From the first concept through a proof of concept to a phased rollout.\n" + "Phased, because a migration done in one go fails on the exceptions.\n" + "\n" + "**Setup and configuration.** The technical side of each service, and the policies behind\n" + "them.\n" + "\n" + "**Operation.** When something sticks later on, we answer.", }, { heading: "

Where it actually gets difficult

", body: "Our work usually starts with Exchange Online and continues with Entra ID. The mailbox\n" + "migration is manageable. Conditional access, guest accounts and the question of who is\n" + "really a Global Administrator take considerably longer.\n" + "\n" + "The second recurring item is storage. It moves from a file server with permissions that\n" + "grew over time into SharePoint, and the permissions move with it. They are best cleaned up\n" + "during the migration.", }, ], }, status: { corpus: 315, services: [ { ref: "services/modern-workplace", score: "0.61", }, { ref: "services/cloud", score: "0.53", }, { ref: "services/digital-workplace", score: "0.44", }, { ref: "services/orchestration-automation", score: "0.43", }, ], experts: [ { ref: "experts/mike-schmid", score: "0.41", featured: true, }, { ref: "experts/matthias-frech", score: "0.48", featured: true, }, { ref: "experts/oliver-erismann", score: "0.47", }, ], neighbours: [ { ref: "solutions/microsoft/microsoft-azure", score: "1.00", }, { ref: "solutions/microsoft/microsoft-365", score: "0.76", }, { ref: "solutions/microsoft/microsoft-teams", score: "0.51", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 70 lines · YAML · validated at build# 106 lines · JSON · validated at build# 106 lines · TOML · validated at build# 125 lines · XML · validated at build# 122 lines · Python · read back at build, equals the JSON record# 119 lines · PowerShell · read back at build, equals the JSON record# 130 lines · Go · read back at build, equals the JSON record# 115 lines · JavaScript · read back at build, equals the JSON record · served at /en/solutions/microsoft.md

Solution · Microsoft

Microsoft

From planning a Microsoft 365 estate through rollout to running it. Most of the effort goes into identity.

Topics Cloud 1.92 Modern Workplace 1.69 Security 1.91

Vendors Microsoft 2.61

04Services

03Capabilities

315Corpus

photograph wantedAn Azure or Microsoft 365 admin surface on screen, being worked in rather than presented

What we do

Planning and design. Choosing the services you actually need, and Microsoft 365 security workshops so the configuration stays sound.

Introduction. From the first concept through a proof of concept to a phased rollout. Phased, because a migration done in one go fails on the exceptions.

Setup and configuration. The technical side of each service, and the policies behind them.

Operation. When something sticks later on, we answer.

Where it actually gets difficult

Our work usually starts with Exchange Online and continues with Entra ID. The mailbox migration is manageable. Conditional access, guest accounts and the question of who is really a Global Administrator take considerably longer.

The second recurring item is storage. It moves from a file server with permissions that grew over time into SharePoint, and the permissions move with it. They are best cleaned up during the migration.