Frequently Asked Questions

List the requirements of each team and device group, then ask what arrangements are available. Any combination of services, eligibility, exclusions, and charges must be confirmed in the applicable written proposal or agreement.

Inventory the users, devices, locations, and applications involved. Identify responsibilities and exclusions explicitly; do not assume that an unlisted person or device is covered.

Record dedicated devices, shared workstations, and other relevant systems. Ask how each proposed billing unit is defined and what it includes or excludes. Compare the actual written scope and charges, not the unit label alone.

Ask which devices and activities a proposed solution covers, who reviews alerts, and what response work is included or excluded. Confirm responsibilities and limitations in writing; a product name does not establish a service commitment.

Identify who owns business accounts, who approves access, and how access changes are handled. Ask what a proposed password-management arrangement includes. Do not share passwords in an initial inquiry.

Identify the email systems involved and ask which controls, administrative tasks, and incident responsibilities are proposed. Confirm product selection, licensing, limitations, and service scope separately.

Ask which sources and information would be checked, what is outside the proposed scope, and who would review or act on findings. Do not assume monitoring or response work is included.

Identify the data, applications, and systems that matter to the business. Ask what would be backed up, how recovery would be checked, and who would perform each task. Retention, recovery arrangements, responsibilities, and any targets need written confirmation.

Ask whether licensing, purchasing, configuration, and ongoing administration are included or excluded, and who is responsible for each. This FAQ does not confirm procurement authority, product availability, or a Microsoft 365 service inclusion.

Existing clients should follow the support instructions agreed for their account. The support request checklist helps prepare details; it is not a submission form. Public phone/email contacts are for general inquiries about support options, not support intake. This website does not create a ticket or establish coverage, priority, availability, or response time. It does not provide emergency or time-sensitive monitoring.

List the equipment, its business use, known issues, and any available lifecycle information. Ask what assessment would be needed before deciding whether to retain or replace it. An inquiry does not establish assessment scope, equipment suitability, or acceptance into a service plan.