search

MicrosoftDocs / CloudAppSecurityDocs

Public repo for CloudAppSecurityDocs-pr
Creative Commons Attribution 4.0 International
107 stars 155 forks source link

Documentation on how to map SaaS ID to a description #618

Closed snowch closed 1 year ago

snowch commented 1 year ago

I couldn't find any documentation on mapping SaaS IDs (e.g. 111161) to a description of the SaaS application.

I have found some info in example code but that's all I could find:

                "service": [
                    {
                        "id": 20893,
                        "label": "Microsoft Exchange Online",
                        "type": "service"
                    },
                    {
                        "id": 11161,
                        "label": "Office 365",
                        "type": "service"
                    },
                    {
                        "id": 12260,
                        "label": "Microsoft Azure",
                        "type": "service"
                    }
                ],
dcurwin commented 1 year ago

@snowch - Can you indicate which page in the documentation this was referring to?

snowch commented 1 year ago

Sorry, I can't remember. I've tried searching, but I could only find a 3rd party example

The main issue for me is that saas ids are frequently referred to in the docs, but I couldn't find any documentation describing how to lookup the saas description from the saas id. Here are some examples of saas ids:

image
image
image

Some of the other data returned by the API is documented allowing you to map a description to an ID for example:

image
dcurwin commented 1 year ago

Thank you for your comment. We'll investigate and get back to you.

batamig commented 1 year ago

Hi @snowch, thanks again for having written into docs. The SaaS IDs listed in docs are only examples and are out of scope for more information in our documentation. If you still need more details, please open a support ticket so that they can understand more about your scenario. I'm going to close this issue for now, but feel free to continue commenting with more feedback about docs. We appreciate your contributions!

please-close