Initial conversation and goals
We understand which partners you work with, which processes the portal should carry and where things stall today.
ICT 365 builds B2B portals on SharePoint Online and Microsoft Entra: supplier and customer portals with guest accounts, onboarding processes, role-based dashboards and secure document exchange. Your partners work with you on a controlled platform instead of email attachments – proven by the partner portal for ArcelorMittal Hamburg GmbH with more than 50 connected partners.
Collaboration with suppliers and customers rarely fails for lack of will – it fails on tools designed for internal teams only. Typical situations:
Quotes, drawings and orders go back and forth as email attachments – without version control.
External users get VPN access or shared accounts because clean guest access is missing.
New suppliers start on forms, phone calls and shoulder taps – and wait weeks for access.
Nobody can prove which partner received which documents, and when.
From the first role concept to day-to-day operation, everything comes from one partner:
The key architecture question: a dedicated portal product – or what your Microsoft 365 tenant can already do?
We build portals as a SharePoint extranet: external users work with guest accounts in Microsoft Entra ID – with multi-factor sign-in, individual permissions and a central lifecycle, without extra infrastructure and without licence costs for a separate portal product. Custom interfaces are built with SPFx and React, the processes behind them with Power Automate. The portal stays part of your existing security and governance landscape – rules such as Conditional Access apply to externals too.
In the Microsoft world there are two routes to a portal – which one fits depends on your partners and scenarios (as of 08/2026):
Our standard route for document collaboration with known partners: guest accounts in Microsoft Entra ID, your existing Microsoft 365 licences and full governance – without a separate portal product.
Microsoft's portal platform for anonymous or very large external scenarios: standalone websites on Dataverse, sign-in through Microsoft Entra External ID, a web application firewall and agent integration via Copilot Studio – licensed separately by user capacity per website. If that is your scenario, we say so honestly – and build it.
A portal is only as good as the control over who sees what.
That is why every portal project includes a clean permission model, traceable approvals and a lifecycle for external accounts – from onboarding to automatic deactivation. Recurring access reviews in Microsoft Entra ID Governance keep guest access verifiable, access is logged. This is also the precondition for safely introducing AI features such as Microsoft 365 Copilot later: what externals must not see, no Copilot may find either.
Five steps from role concept to a running portal – first partners already work in the pilot phase.
We understand which partners you work with, which processes the portal should carry and where things stall today.
Portal structure, onboarding flow and permission model – as a concept with a reliable effort estimate.
An early prototype shows dashboard and flows; from there the portal grows in short iterations.
Selected partners work in the portal for real, their feedback flows straight in – then comes the wider rollout.
Support, monitoring and the management of external accounts across their whole lifecycle.
For ArcelorMittal Hamburg GmbH we rebuilt supplier collaboration – a SharePoint-based portal connects buyers and suppliers and makes the exchange of documents and information secure.
Something still open? Ask us directly – in your initial conversation or by phone at +49 651 49364480.
It depends on the scope: the number of processes, the complexity of onboarding and the degree of customisation drive the effort. After the concept phase you receive a reliable estimate. There are no running licence costs for a separate portal product – the portal runs in your Microsoft 365 tenant.
A focused portal with a clear onboarding process goes live much faster than a platform with many integrated processes – an honest answer follows the concept phase. Thanks to prototype and pilot, first partners work in the portal early, before everything is finished.
Usually no: external users work through guest accounts in Microsoft Entra ID, and sharing SharePoint content with guests is part of Microsoft 365. Whether your scenario has special cases is something we check in the concept phase – you do not have to buy licences for every partner.
Guest accounts are subject to the same mechanisms as internal ones: multi-factor sign-in, Conditional Access, individual permissions and logging. On top comes a lifecycle process that detects and deactivates unused accounts – control is part of the concept, not an accessory.
Yes. Besides classic guest invitations, third-party identity providers can be connected – today through Microsoft Entra External ID – so partners use their existing company logins. That lowers onboarding hurdles and avoids password sprawl on the partner side.
For typical supplier and customer collaboration with known partners, usually not: the SharePoint extranet uses your existing licences and governance. Power Pages plays to its strengths when many external or anonymous users need a standalone web application – it is then licensed by user capacity per website (as of 08/2026). We recommend the route that fits your scenario, not the one with the biggest licence bill.
Yes – via connectors, APIs and Azure services we integrate existing systems, for example for order or supplier master data. The key is to clarify early which system leads; integrations like these are part of our standard scope.
Governance
In many companies governance is neglected and harbours risks such as data loss. We help you secure your systems.
Learn more →
Application Development
We have developed hundreds of business-critical applications. Let your next important project be one of them.
Learn more →
Process Automation
We automate business-critical processes to save costs and reduce risks.
Learn more →An initial conversation takes 30 minutes and costs nothing. Afterwards you will know which portal route fits your partners – and what onboarding can look like.
ICT 365 Solutions GmbH · Bobinethöfe 54 · 54294 Trier