build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Solutionmetadata: name: microsoft locale: en labels: vendor: Microsoft capability/cloud: 1.94 capability/modern-workplace: 2.11 capability/security: 2.16 vendor/microsoft: 2.53 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. The demanding part is rarely the technology, it is the 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 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 rather than on the mailboxes. **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: | We get called in for Exchange Online and stay for 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 fifteen years into SharePoint, and the permissions move with it. A migration is the only good moment to clean that up.status: corpus: 267 services: - {ref: services/modern-workplace, score: 0.61} - {ref: services/cloud, score: 0.52} - {ref: services/digital-workplace, score: 0.45} - {ref: services/orchestration-automation, score: 0.42} posts: - {ref: posts/how-to-igel-ud-pocket-bios-uefi-settings, score: 0.39} - {ref: posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos, score: 0.39} - {ref: posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem, score: 0.39} - {ref: posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem, score: 0.39} - {ref: posts/send-workspace-one-hub-notifications, score: 0.39} - {ref: posts/how-to-build-a-test-environment-for-opswat-metadefender-managed-file-transfer, score: 0.39} experts: - {ref: experts/matthias-frech, score: 0.46} - {ref: experts/mike-schmid, score: 0.42} - {ref: experts/aldo-gwerder, score: 0.41} neighbours: - {ref: solutions/microsoft/microsoft-azure, score: 1.00} - {ref: solutions/microsoft/microsoft-365, score: 0.78} - {ref: solutions/microsoft/microsoft-teams, score: 0.54}
{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "microsoft", "locale": "en", "labels": { "vendor": "Microsoft", "capability/cloud": "1.94", "capability/modern-workplace": "2.11", "capability/security": "2.16", "vendor/microsoft": "2.53" }, "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. The demanding part is rarely the technology, it is the 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" }, "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 rather than on the\nmailboxes.\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": "We get called in for Exchange Online and stay for Entra ID. The mailbox migration is\nmanageable. Conditional access, guest accounts and the question of who is really a Global\nAdministrator take considerably longer.\n\nThe second recurring item is storage. It moves from a file server with permissions that\ngrew over fifteen years into SharePoint, and the permissions move with it. A migration is\nthe only good moment to clean that up." } ], "status": { "corpus": 267, "services": [ { "ref": "services/modern-workplace", "score": "0.61" }, { "ref": "services/cloud", "score": "0.52" }, { "ref": "services/digital-workplace", "score": "0.45" }, { "ref": "services/orchestration-automation", "score": "0.42" } ], "posts": [ { "ref": "posts/how-to-igel-ud-pocket-bios-uefi-settings", "score": "0.39" }, { "ref": "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos", "score": "0.39" }, { "ref": "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem", "score": "0.39" }, { "ref": "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem", "score": "0.39" }, { "ref": "posts/send-workspace-one-hub-notifications", "score": "0.39" }, { "ref": "posts/how-to-build-a-test-environment-for-opswat-metadefender-managed-file-transfer", "score": "0.39" } ], "experts": [ { "ref": "experts/matthias-frech", "score": "0.46" }, { "ref": "experts/mike-schmid", "score": "0.42" }, { "ref": "experts/aldo-gwerder", "score": "0.41" } ], "neighbours": [ { "ref": "solutions/microsoft/microsoft-azure", "score": "1.00" }, { "ref": "solutions/microsoft/microsoft-365", "score": "0.78" }, { "ref": "solutions/microsoft/microsoft-teams", "score": "0.54" } ] }}
apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "microsoft"locale = "en"[metadata.labels]vendor = "Microsoft""capability/cloud" = "1.94""capability/modern-workplace" = "2.11""capability/security" = "2.16""vendor/microsoft" = "2.53"[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. The demanding part is rarely the technology, it is the 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"[[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 rather than on themailboxes.**Setup and configuration.** The technical side of each service, and the policies behindthem.**Operation.** When something sticks later on, we answer.'''[[sections]]heading = "

Where it actually gets difficult

"
body = '''We get called in for Exchange Online and stay for Entra ID. The mailbox migration ismanageable. Conditional access, guest accounts and the question of who is really a GlobalAdministrator take considerably longer.The second recurring item is storage. It moves from a file server with permissions thatgrew over fifteen years into SharePoint, and the permissions move with it. A migration isthe only good moment to clean that up.'''[status]corpus = 267[[status.services]]ref = "services/modern-workplace"score = "0.61"[[status.services]]ref = "services/cloud"score = "0.52"[[status.services]]ref = "services/digital-workplace"score = "0.45"[[status.services]]ref = "services/orchestration-automation"score = "0.42"[[status.posts]]ref = "posts/how-to-igel-ud-pocket-bios-uefi-settings"score = "0.39"[[status.posts]]ref = "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos"score = "0.39"[[status.posts]]ref = "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem"score = "0.39"[[status.posts]]ref = "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem"score = "0.39"[[status.posts]]ref = "posts/send-workspace-one-hub-notifications"score = "0.39"[[status.posts]]ref = "posts/how-to-build-a-test-environment-for-opswat-metadefender-managed-file-transfer"score = "0.39"[[status.experts]]ref = "experts/matthias-frech"score = "0.46"[[status.experts]]ref = "experts/mike-schmid"score = "0.42"[[status.experts]]ref = "experts/aldo-gwerder"score = "0.41"[[status.neighbours]]ref = "solutions/microsoft/microsoft-azure"score = "1.00"[[status.neighbours]]ref = "solutions/microsoft/microsoft-365"score = "0.78"[[status.neighbours]]ref = "solutions/microsoft/microsoft-teams"score = "0.54"
<?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.94</entry> <entry key="capability/modern-workplace">2.11</entry> <entry key="capability/security">2.16</entry> <entry key="vendor/microsoft">2.53</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. The demanding part is rarely the technology, it is the 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> </spec> <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 rather than on themailboxes.**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>We get called in for Exchange Online and stay for Entra ID. The mailbox migration ismanageable. Conditional access, guest accounts and the question of who is really a GlobalAdministrator take considerably longer.The second recurring item is storage. It moves from a file server with permissions thatgrew over fifteen years into SharePoint, and the permissions move with it. A migration isthe only good moment to clean that up. </body> </section> </sections> <status> <corpus>267</corpus> <services> <item> <ref>services/modern-workplace</ref> <score>0.61</score> </item> <item> <ref>services/cloud</ref> <score>0.52</score> </item> <item> <ref>services/digital-workplace</ref> <score>0.45</score> </item> <item> <ref>services/orchestration-automation</ref> <score>0.42</score> </item> </services> <posts> <item> <ref>posts/how-to-igel-ud-pocket-bios-uefi-settings</ref> <score>0.39</score> </item> <item> <ref>posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos</ref> <score>0.39</score> </item> <item> <ref>posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem</ref> <score>0.39</score> </item> <item> <ref>posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem</ref> <score>0.39</score> </item> <item> <ref>posts/send-workspace-one-hub-notifications</ref> <score>0.39</score> </item> <item> <ref>posts/how-to-build-a-test-environment-for-opswat-metadefender-managed-file-transfer</ref> <score>0.39</score> </item> </posts> <experts> <item> <ref>experts/matthias-frech</ref> <score>0.46</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.42</score> </item> <item> <ref>experts/aldo-gwerder</ref> <score>0.41</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.78</score> </item> <item> <ref>solutions/microsoft/microsoft-teams</ref> <score>0.54</score> </item> </neighbours> </status></manifest>
Solution · Microsoft

Microsoft

From planning a Microsoft 365 estate through rollout to running it. The demanding part is rarely the technology, it is the identity.

Topics Cloud 1.94 Modern Workplace 2.11 Security 2.16
Vendors Microsoft 2.53
04Services
06Posts
03Capabilities
267Corpus

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 rather than on the mailboxes.

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

We get called in for Exchange Online and stay for 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 fifteen years into SharePoint, and the permissions move with it. A migration is the only good moment to clean that up.

Posts about it

Who works with it

Do you work with this? Take a look at our open roles.