You have a server that runs Windows Server and has the DHCP Server role installed.

Windows Server DHCP policies let an administrator define conditions, such as a MAC address prefix/range or vendor class, and, when a requesting client matches those conditions, assign it an address from a specific sub-range carved out within an existing scope, all without creating a second scope or disturbing how other clients in that same scope are served. Because all 50 Teams Phone devices share MAC addresses within a known, identifiable range, a policy can match on that MAC prefix and hand out addresses only from 192.168.1.100–192.168.1.200, while every other client in Scope1 continues to receive addresses from the rest of the pool as before, exactly matching the requirement to not affect other clients. Creating a second scope would require a distinct, non-overlapping subnet and would not let two scopes share the same 192.168.0.0/23-style address space as described. A DHCP filter (allow/deny list) can only permit or block specific MAC addresses from getting a lease at all; it has no ability to steer a matched device into a particular IP sub-range. Scope options configure settings such as DNS servers or default gateway for the whole scope and have no address-targeting capability. A policy is therefore the correct feature to create.