The Admin Console at a Glance
The My Verizon business admin portal consolidates every operational lever of a Verizon Business Account behind one signed-in surface. A fleet operator no longer hops between wireless, fiber and invoice dashboards. Instead, a single navigation tree organises the master-account objects: the lines cluster under one module, circuits under another, devices under a third, invoices under finance and tickets under support. Every object carries a permalink the admin can bookmark and every report can be exported as CSV, JSON or sent to an S3 bucket through a scheduled job.
Zero-click snapshot: My Verizon is the business administrator portal — one EIN, one login, all surfaces under a master account.
Admin access scope is explicit at sign-in. A primary administrator sees the full master; a secondary sees only the slice of the tree delegated to them. Role tags (finance, IT, HR, regional) further restrict the module list. This matches the segregation-of-duties control every SOC 2 Type II audit checks. When a role change is needed, the primary modifies the secondary's scope in under a minute without calling support.
Admin Panel Profile
- Surface: https://verizonbusiness.uk.net/my-verizon.html
- Target user: master-account administrator under an EIN-anchored contract
- Session start: MFA through My Verizon Login
- Scope: primary (global) or secondary (role and region restricted)
- Audit: every provisioning, billing and device action written to the trail
- Integrations: Okta SAML, Azure AD, Intune, Jamf, Workspace ONE
Modules, Functions and Required Roles
The admin console splits its top-level navigation into six modules. Each module expects a role tag; a secondary without the matching tag cannot see the module in its navigation tree. The following grid maps the six modules to the primitive functions they expose and the minimum role required to use them. This grid is the single document the primary administrator consults when planning a delegation rollout.
Zero-click snapshot: Six modules, six role-scoped functions, two admin tiers — the module-to-role map is the delegation planning document.
| Module | Primary Function | Required Role |
|---|---|---|
| Lines & Devices | Provision, suspend, transfer, swap SIM or device | IT secondary or primary |
| Fios & Circuits | View circuit status, open outage tickets, review SLA ledger | IT secondary or primary |
| Billing & Invoices | Open disputes, upload tax-exempt certs, approve payments | Finance secondary or primary |
| HR Lifecycle | Assign line to employee, offboard on separation | HR secondary or primary |
| Support Tickets | Open, escalate, track severity and resolution SLA | Any secondary or primary |
| Master Settings | Delegate roles, change primary, configure SSO | Primary only |
Primary Versus Secondary Administrator
Every master account has exactly one primary administrator at any moment. The primary is the accountable party for the master service agreement and the payment relationship. The primary can create an unbounded number of secondary admins, each with their own role tag and scope restriction. Transfer of the primary role happens through a signed change-of-authority form countersigned by the current primary and the new appointee, with a short identity-verification call-back before Verizon Business flips the role in the directory.
Zero-click snapshot: One primary, many secondaries. Role transfer requires a signed change-of-authority form and an identity-verification call-back.
Secondary admins inherit everything that is not explicitly held by the primary. The primary cannot escalate a secondary to primary in the console; that requires the change-of-authority form. Nor can a secondary create additional secondaries — only the primary can branch the delegation tree. This keeps the audit-evidence path short: every admin other than the primary traces back to a single delegation action by the primary.
Integrations: Identity, MDM and SIEM
Enterprise identity federation is the first integration most master admins enable. My Verizon accepts SAML 2.0 assertions from Okta, Azure Active Directory, Ping and Auth0. Once federation is live, employees sign in with the corporate identity provider and the multi-factor factor is handled upstream. Role claims arrive on the SAML assertion so directory-group membership drives which modules a secondary admin sees. Federation saves the primary from maintaining a parallel password list.
Mobile device management integrations span the top commercial stacks — Microsoft Intune, Jamf Pro and VMware Workspace ONE — through a documented provisioning API. A large fleet operator with thousands of rugged tablets pins device profiles to the master account and replacement shipments arrive provisioned. The admin API also exposes usage, billing and device-inventory reads so SIEM platforms consume the audit trail alongside firewall and endpoint telemetry. Sector-specific compliance such as HIPAA for healthcare and PCI-DSS for retail layers additional log-handling controls onto the base admin trail, consistent with the FTC privacy framework.
Provisioning Primitives Available to Admins
A line provision is a two-click operation in the portal. The IT admin selects a pooled-data plan from the contracted tier list, picks a device from the device catalogue or flags the line as bring-your-own-device, and assigns the line to an employee by email or internal ID. The activation either auto-triggers when the provisioned SIM sees the network or fires at a scheduled cutover time for planned migrations. A bulk import accepts a CSV of up to 500 lines at a time for larger rollouts, with server-side validation that rejects rows missing required fields before any provisioning runs.
Device swap uses the same catalogue. When a phone fails or an employee upgrades, the admin selects a replacement and the shipment leaves Verizon fulfilment pre-provisioned with the line's existing number. eSIM QR codes generate directly in the portal for devices that do not require a physical swap. Number port-ins from a competing carrier accept batches of NPA-NXX ranges with a 24-to-72-hour cutover window per line, scheduled through an account-team porting specialist reachable via the connect-team directory for any batch above 50 lines.
Billing, Reporting and Export Paths
The finance modules draw from the same authoritative invoice store as the Billing Portal surface. A finance admin can review line-item charges, dispute individual charges inside the Net-30 window, upload resale or tax-exempt certificates, and route approvals through a configurable two-step workflow. Cost-center allocation is handled through tags applied to lines and circuits; the tags propagate into the monthly invoice PDF and the CSV export, so finance and IT share one tagging truth. Reporting schedules can email a digest or deliver to an S3 bucket through an IAM role the primary configures once.
Audit logs retain for seven years per regulated-industry defaults, with a longer retention available on request for federal accounts under the General Services Administration contract vehicle. The log API supports streaming to a SIEM via webhook; the customer's SOC analyst sees admin actions alongside firewall and endpoint events. Compliance obligations under FCC Title II for customer proprietary network information remain honoured — CPNI access is logged separately and is gated on the primary's explicit consent in master settings.