Skip to content

IT services

Workplace information and device projects

Organise shared information, configure devices and introduce new ways of working through a defined project. Subnet can help scope and deliver workplace changes, with access, rollout checks and staff guidance agreed for the engagement. Start with the teams and tasks affected, then plan the technology around them.

WORK WITH SUBNET

Intune endpoint management

Endpoint management connects devices, applications and policy. Subnet can scope Intune implementation work around the devices and operating requirements in your environment, with enrolment, configuration, deployment and handover agreed before delivery.

Confirm the required licensing and supported platforms. An Intune project does not automatically include every add-on or replace all existing device-management responsibilities.

WORK WITH SUBNET

Microsoft 365 migration and tenancy changes

Moving email or separating a business into a new Microsoft 365 tenant starts with understanding what needs to move and who can access the source environment. Subnet can scope Exchange-to-Microsoft 365 migrations and selected tenancy changes, with the migration method, identity preparation and cutover responsibilities agreed before work begins.

Relevant work may include directory and sign-in preparation, agreed mailbox migration, validation and handover. File migration to SharePoint and changes to endpoint configuration can be added where required, with their own dependencies and acceptance checks.

Source-administrator access and licensing affect the available approach. Mail migration alone does not include SharePoint migration, device enrolment, server retirement or all end-user assistance. Agree these workstreams and support responsibilities explicitly.

WORK WITH SUBNET

Identity, MFA and single sign-on

Access controls should reflect the people, devices and applications they protect. Subnet can scope selected Microsoft Entra ID sign-in and Conditional Access changes, Windows Hello for Business pilots, and defined MFA or single sign-on work for agreed applications and user groups.

Start by mapping the required access and checking device, policy and licensing prerequisites. Depending on the design, work may include policy configuration, Windows Hello for Business trust preparation, representative-user testing or a separately scoped Duo-protected access path.

Authentication and device compliance are separate controls. Agree how each will be checked, which users and devices are covered, and who completes production rollout and user support. Shared-device scenarios and application-specific requirements need assessment rather than a standard rollout assumption.

WORK WITH SUBNET

Device deployment and staff changeovers

A device refresh needs a practical plan for getting people onto their new equipment. Subnet can scope distributor-prepared or directly configured endpoints, agreed account and device changeovers, and administration for retiring replaced devices.

Define the applications, enrolment requirements, user steps and acceptance checks before deployment. Device preparation and the underlying Intune configuration are related workstreams, with responsibilities agreed for each.

End-user completion, travel, desk setup and disposal are included only where specified. Confirm who handles data transfer, physical installation and support during the changeover, rather than assuming that a hardware order includes the complete rollout.

WORK WITH SUBNET

Voice and telephony transitions

A phone-system change affects numbers, call flows, staff devices and the network. Subnet can scope voice transitions that coordinate the provider's platform work with agreed porting, network preparation, client deployment and administration tasks.

For selected Access4 services, the provider may lead platform and call-flow configuration while Subnet handles the agreed local deployment and transition work. Handsets, existing-system decommissioning and staff training can be included when specified. Confirm the responsibilities of each provider and the dependencies that affect the changeover.

Teams Phone arrangements vary, and not every deployment uses Access4. Number porting is subject to the relevant providers' processes. Meeting-room audiovisual work, fax changes and wider collaboration projects require their own scope where needed.

WORK WITH SUBNET

SharePoint, Teams and OneDrive collaboration

Moving files is an opportunity to agree how work should be organised. Define sites, libraries, owners and access before migrating content. Map source folders to their destinations, test representative files and permissions, then agree cutover and user handover. Where Teams is used, its membership and channel structure need to align with the connected SharePoint environment.

Agree what remains, what moves and how users will find and share information afterwards. Additional intranet development, custom workflows or a broad change-management programme are separately defined.

WORK WITH SUBNET

Information governance and AI readiness

Review content ownership, permissions and sharing alongside classification, information protection and retention requirements. Where Microsoft Purview is appropriate, agree the policy purpose, users, workloads, owners and licensed coverage before selecting an implementation scope.

A Microsoft security deployment does not automatically include a Purview classification programme. Governance work supports readiness; it is not a guarantee of legal compliance or a substitute for correcting excessive access.

Start with the work that needs to change

A workplace project might begin with a new collaboration space, inconsistent device settings or a change in how staff access their working environment. Identify the everyday tasks that need to work better and the people who can decide what good looks like.

Information ownership matters as much as the configuration. Before changing a shared workspace, establish who owns its content, who should have access and which decisions need approval. For devices, identify the applications, access and support arrangements each affected group needs.

Define the part of the workplace you want to improve

Shared information and collaboration spaces

Scope the setup or adjustment of collaboration areas, information structures and settings. Agree what stays, what changes and who owns the result. Any content move, version-history requirement or clean-up needs to be defined rather than assumed.

Devices and working environments

Plan the configuration or rollout of the devices and desktop environment in scope. Identify the users, applications, access requirements and existing equipment involved. Confirm licensing and compatibility before selecting the deployment approach.

Staff guidance and adoption

Identify the tasks people need to learn and the support they will use during the change. Training, administrator guidance and handover can be included where agreed, with the audience and materials defined in the project brief.

A rollout with clear approval points

Map the current arrangements

Record the affected teams, information locations, device groups and existing access. Identify missing decisions, dependencies and the people who can approve changes.

Agree the configuration and scope

Set the intended structure, access rules and device configuration. Confirm what will be migrated, configured or retained, alongside exclusions and any work owned by another provider.

Test with representative users

Use an agreed group to check real tasks and access boundaries. Record issues before wider rollout and give the business owner a clear point to approve, refine or pause the change.

Roll out and hand over

Sequence the approved work around business needs. Make staff guidance, open issues and support ownership part of the handover, so the team operating the result knows what changed.

Check the result through everyday tasks

Acceptance should include the people who will use and manage the new arrangement. Agree the test cases and evidence before rollout, rather than treating configuration alone as completion.

  • Information: representative users can find and work with the agreed content, and the required content or history has been checked.
  • Access: people can reach the information and services intended for their role, while restricted content remains unavailable to those who should not see it.
  • Devices: nominated users can sign in, use the required applications and complete the tasks in the test plan.
  • Handover: the service owner knows how to request changes, where to find operating information and who handles outstanding issues.
An example of a collaboration-space project

Illustrative example: a team wants a shared place for working documents with clear ownership and access.

The team nominates a content owner and identifies which people need to read or edit each area. The project scopes the workspace setup and any content transfer. A representative set of documents and users is used to check organisation, access and common tasks before the wider change is approved.

The owner reviews the results and unresolved items. Staff receive the agreed guidance on where to work and how to request access, while the support team receives the operating information included in the project. Success measures could include completed task checks, verified access rules and open issues with named owners.

Make the project boundary explicit

A scoped workplace project can address one area without redesigning the entire environment. The proposal should identify the users, information, devices and activities covered, together with the decisions that remain with your organisation.

  • Customer responsibilities: nominate information and application owners, approve access, provide authorised system access and make representative users available for testing.
  • Prerequisites: suitable licences, supported applications and devices, connectivity, source information and cooperation from any other providers.
  • Separate work where needed: extensive data clean-up, custom application development, infrastructure replacement, network changes and broader security remediation.
  • Commercial scope: equipment, subscriptions, migration tools, training and post-rollout assistance are included only where specified.
  • Ongoing ownership: agree who will maintain content, manage access and devices, and provide support after the project.
A published example of changing the way staff work

Subnet’s District Council of Yankalilla case study describes a transition from thin clients to laptops, alongside work to enable remote working. The change formed part of a tailored upgrade plan developed with the council.

Read the District Council of Yankalilla case study

Published customer feedback

“I would definitely recommend Subnet to other Councils - they're like having expert support in your pocket.”

Jodie Summer, Executive Manager - Financial Sustainability, District Council of Yankalilla, as attributed in Subnet’s published case study (5 January 2026).

Questions about workplace information and device projects

Do we need to change every part of our workplace technology?

No. The brief can focus on a collaboration space, a device group or a defined part of the working environment. Identify the dependencies so that a smaller change does not leave an important access, application or support decision unresolved.

Will existing access permissions be carried across unchanged?

Do not assume that copying the current arrangement is the right outcome. Agree the intended access with the information owner, then check it during the project. Any migration should include the access checks appropriate to its scope and the systems involved.

Can we retain our current devices and applications?

Discuss what you want to retain during scoping. Compatibility, support status, licences and the requirements of affected users need to be checked. The agreed design should make any replacement or application change clear before rollout.

Are software licences and new devices included?

Only if the proposal includes them. Separate the implementation work from equipment, subscriptions and any migration tools so the full cost and ongoing commitments are visible.

Does the project include staff training?

Training can be scoped around the affected roles and tasks. Confirm the audience, format, materials and any administrator handover in the proposal. A technical deployment alone does not define the level of user support included.

Who manages the environment after rollout?

Agree that before delivery. Content owners, administrators and the support team may have different responsibilities. Record who approves access changes, maintains the configuration and handles requests, with any ongoing managed service specified separately.

What should we arrange before a Microsoft 365 migration starts?

Work out who holds administrator access to the current email system, and confirm licensing early, because both affect which approach is available. You will also need to nominate owners and make authorised access available. Microsoft documents several routes for moving Exchange mailboxes, including cutover, staged, hybrid and IMAP, chosen by source system and size. IMAP, for example, does not carry contacts, calendars or tasks, and mailboxes must exist before it runs. The method is agreed before cutover.

How do we decide which files move to SharePoint and which stay behind?

Start with decisions rather than tools. Define sites, libraries, owners and access, then map source folders to destinations and test representative files and permissions before agreeing cutover. Microsoft’s SharePoint Migration Tool lists file shares as a supported source, but choosing a tool does not settle what should move, who owns it or who can see it. Anything left behind, and how people will find it afterwards, should be agreed up front.

What should we confirm before moving to Teams Phone?

Teams Phone arrangements vary, and not every deployment uses Access4. Microsoft describes different ways to connect Teams to the phone network, including Calling Plans, Operator Connect and Direct Routing, and each divides responsibility between you and the provider differently. Users also need the right Teams Phone licence. For selected Access4 services, the provider may lead platform and call-flow work while Subnet handles the agreed local deployment and transition tasks. Handsets, decommissioning and training are included only when specified.

Can we keep our existing phone numbers?

Usually, when changing providers, but it depends on the number and the providers involved. Number porting follows the relevant providers’ processes. The Australian Communications and Media Authority explains that you request the port through the new provider, who runs identity checks, that the new provider is not obliged to accept a ported number, and that disconnected numbers cannot be ported. Mobile ports are typically quick while landlines can take longer, so plan the changeover around the slowest number.

BEFORE WE TALK

A useful starting point.

You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.

  • What decision or change do you need to make?
  • What is known about the current environment?
  • What needs to be agreed about scope, dependencies and handover?
Discuss these priorities

LET’S TALK

WHAT WOULD YOU LIKE TO DO NEXT?

Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.

Prefer to talk?(08) 7127 9400Already a customer and need help? Go to Support.
PROPOSED FORM · PRIVATE PREVIEW ONLY

Preview only. Nothing is sent, stored or booked.

A live version will need final routing, consent and privacy review. Subnet privacy policy

Contact us