Screen flows do not ship with a standard map component. Here are your real options, side by side.
The Avonni Map inside a screen flow, recorded in a Salesforce org. Picking a marker hands that record to the next screen. Fictional data.
One click, three things happen. Here is the sequence, screen by screen.



No Apex, no deploy. The configuration happens in the component builder, inside Flow Builder.
Avonni Flow Screen Components, in production or in a sandbox. Start free opens both links.
Pick Google Maps or Leaflet, point it at an object with an address or coordinates, choose what each marker shows.
Add an interaction on marker select, or read the selected record on the next screen. Then test with Previous and Next.
Google Maps or Leaflet, chosen in the builder.
Custom markers for the records you query, clustered on Leaflet.
Draw zones and shapes on the Leaflet map, saved as a file if you want.
Select a marker and the record flows into your next screen.
Search across record fields and filter by field, right on the map.
Street, city, postal code on Google Maps. Coordinates on Leaflet.
Paths 2 and 3, side by side. A custom flow screen component is a Lightning Web Component you build and maintain yourself.
Work from addresses in a list or table inside the flow. It works, but your users lose the spatial view.
A custom Lightning Web Component on the lightning map base component. You write, test, and deploy it.
Installed from AppExchange, configured in the builder, live inside your flow. No code.
Avonni Flow Screen Components. Free sandbox, 10 free production licenses. Start free opens the install links for both.