Reference:
In Windows Server DHCP, policies let you "assign different options or even different IP address ranges to clients that meet specified conditions." The AZ-800 study guide explains that scope-level policies can target clients by MAC address (Client Identifier), vendor class, user class, relay agent, or other fields, and when a lease is requested, "the DHCP server evaluates policies in order; if a client matches a policy, the server can allocate an address from the policy's configured IP range and apply policy-specific options, without affecting other clients in the scope." This is distinct from filters, which only allow or deny clients based on MAC and do not select an address pool; scope options merely set option values (DNS, router, etc.) and cannot constrain the lease address range; creating another scope would require a different subnet or superscope and would change allocation behavior for the entire network.
Given Scope1 (192.168.0.0/23) already serves all clients, and only the Teams Phone devices (all MACs in a common range) must receive addresses 192.168.1.100-192.168.1.200 without impacting others, the correct solution is to create a DHCP policy on Scope1 with a condition matching that MAC address range and configure the policy's IP address range to 192.168.1.100-192.168.1.200. This fulfills the requirement while leaving all other clients to receive addresses from the normal Scope1 pool.