Scribd Logo
Upload

Welcome to Scribd!

  • 412 views

    Sow m356 Basic To Intune

    Uploaded by

    Richard Zecchino
    This document defines the scope of work for migrating an organization from Microsoft 365 Basic Mobility and Security to Intune. The migration will involve discovering existing devices and policies, planning the migration steps, configuring and testing Intune, deploying it to devices, and documenting the new configuration. The estimated timeline is 6-8 weeks. Key deliverables will be a migration plan, documentation of Intune configuration and policies, and test results.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Sow m356 Basic To Intune

    Uploaded by

    Richard Zecchino
    412 views2 pages
    This document defines the scope of work for migrating an organization from Microsoft 365 Basic Mobility and Security to Intune. The migration will involve discovering existing devices and policies, planning the migration steps, configuring and testing Intune, deploying it to devices, and documenting the new configuration. The estimated timeline is 6-8 weeks. Key deliverables will be a migration plan, documentation of Intune configuration and policies, and test results.

    Original Description:

    migrate from m365 basic security to intune

    Original Title

    sow m356 basic to Intune

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document defines the scope of work for migrating an organization from Microsoft 365 Basic Mobility and Security to Intune. The migration will involve discovering existing devices and policies, planning the migration steps, configuring and testing Intune, deploying it to devices, and documenting the new configuration. The estimated timeline is 6-8 weeks. Key deliverables will be a migration plan, documentation of Intune configuration and policies, and test results.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    412 views2 pages

    Sow m356 Basic To Intune

    Uploaded by

    Richard Zecchino
    This document defines the scope of work for migrating an organization from Microsoft 365 Basic Mobility and Security to Intune. The migration will involve discovering existing devices and policies, planning the migration steps, configuring and testing Intune, deploying it to devices, and documenting the new configuration. The estimated timeline is 6-8 weeks. Key deliverables will be a migration plan, documentation of Intune configuration and policies, and test results.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    The purpose of this Statement of Work (SOW) is to define the scope of work and deliverables required

    for the successful migration from Microsoft 365 Basic Mobility and Security to Intune. This migration will
    provide advanced device management and security capabilities that will enhance the organization's
    ability to protect its assets and data.

    Scope of Work: The scope of work includes the following activities:

    1. Discovery: Perform an inventory of all devices managed by Microsoft 365 Basic Mobility and
    Security and document any custom policies or configurations that have been applied.

    2. Planning: Develop a migration plan that outlines the steps required to move from Microsoft 365
    Basic Mobility and Security to Intune, including any necessary changes to policies or
    configurations.

    3. Configuration: Configure Intune to align with the organization's security and device
    management requirements, including setting up policies, configuring enrollment settings, and
    testing policies.

    4. Pilot: Conduct a pilot test to validate the functionality of Intune and to ensure that all devices
    can be enrolled and managed as expected.

    5. Deployment: Deploy Intune to all applicable devices, including communication and training for
    end-users.

    6. Testing: Conduct testing to ensure that Intune is fully functional and that all devices are being
    managed and secured as intended.

    7. Documentation: Provide documentation outlining the configuration and policies applied in


    Intune.

    Deliverables: The following deliverables will be provided as part of this migration:

    1. Migration Plan: A detailed migration plan outlining the steps required to move from Microsoft
    365 Basic Mobility and Security to Intune.

    2. Configuration Documentation: Documentation outlining the configuration and policies applied in


    Intune.

    3. Testing Results: Documentation detailing the results of testing conducted to ensure that Intune
    is fully functional and that all devices are being managed and secured as intended.

    Timeline: The estimated timeline for this migration is 6-8 weeks, dependent on the size and complexity
    of the organization's device inventory and existing policies.

    Assumptions: The successful completion of this migration is dependent on the following assumptions:

    1. The organization has a valid Microsoft Intune license.

    2. All applicable devices are running supported operating systems and have internet access.

    3. The organization will provide access to necessary resources, including devices and network
    access.
    Conclusion: This Statement of Work outlines the scope of work and deliverables required for a
    successful migration from Microsoft 365 Basic Mobility and Security to Intune. This migration will
    enhance the organization's ability to protect its assets and data by providing advanced device
    management and security capabilities.

    You might also like