 Samira says, hello, I want to create a flow that can convert the Excel files extension from XLSM to XLSX and upload it into a SharePoint. I want to know if a model that can do this action exists in Power Automate. I believe you can do a file save as, but there's some cautions that you need to know. The XLSM extension is a macro-enabled Excel file, and if you load that into the browser as an XLS, those automations no longer work, which is a safety thing. There's script that runs those, can actually touch all the way to your machine. It can activate and do things to your computer with that VBA Visual Basic programming languages behind those. It's dangerous and you want to make sure that all of your files that have the M extension instead of just the X, are either stored in a trusted location or when you open them, you can store them in a SharePoint document library, but that document library, you have to either enable the file to be opened directly into the desktop application. You cannot open and do any of those automations in the browser. There's some cautions on that one. If you had that in that SharePoint library, without taking those additional steps, would it just not open? Would it throw an error? It would open, but it would definitely give you the nasty gram that there are macros in here that have been disabled, and it's because there's script, there's actual. This is one of the ways, if you ever get those emails are like, open this email because somebody sent you money and you open a file and it actually runs a script because there's an on opened that is attached to that. So this is for the safety of the people that are using these files. You need to know where they're coming from, who wrote them, and then designate. The best thing to do best practice is create a trusted location on your computer, which could be a synced OneDrive, which is what I do. It's either OneDrive or a SharePoint library. They sync to the local drive where the M files are and I open them from there. I don't open them from the browser because they will deactivate the macros on the browser. But yeah, this is a whole lot of caution, and it depends and be wears in this question. So I don't know that I would add an automation on top of a file that's already got script in it. That's a little dangerous, I think. Well, did we answer the second half of the question though? There's you can convert and it breaks the macros, is there maybe they don't care about that, and just want to do the conversions. Is that something, is there a Power Automate command that can rename file extensions? File save as, you can do file saving, you can save any file as an extension. I'll look to see, I'll do some research and see if I can find a resource for that. I've never done it, but I also didn't want people like, oh, this is a great idea without knowing all of the pitfalls behind it. I'll do some research.