[jayturley]

In standard scrum, the Scrum Master is responsible for managing the process around developing software, not for actually estimating, creating features, tracking, etc. A Scrum Master's tasks remain the same regardless of what product is being worked on. A Product Owner would be closer to the role you describe above.

As a SWE who moved to Agile Coach, it can be a fun challenge, but since you aren't actually doing scrum, you shouldn't worry about actually following the full process and instead should think about essentially being a product owner (no matter the title) - the interface between the development team and the customer. You'll want to watch out for you being held responsible for the team's performance instead of the ICs on the team. So some CYA could be in order, even if that's just clearly defining your roles and deliverables with management before taking it on.

As another commenter noted, you should be able to lean on your team for help with things like estimation and tracking, but that really depends on your organization's existing process.