After creating a new Defender EASM instance to discover externally facing assets, what is the next action you should take?

After creating a new Defender EASM instance, the immediate next step is to import seeds from your organization. Seeds are known assets (like domain names, IP addresses, or email contacts) that Defender EASM uses as starting points to discover your entire external attack surface. Without seeds, the instance has no initial information to begin its discovery process. Creating a custom attack surface is a subsequent step, refining the discovered assets. Adding a Log Analytics workspace is for logging and monitoring, not initial discovery. Adding a discovery group is also a later organizational step for managing discovered assets.