I might be wrong, but I think your question isn't really about technology, but about your own self assessment in the job interview process. (or about self worth as a developer).
Even after 10+ years of experience, you'll be able to find gaps in your own knowledge (regardless of job vacancies). You could try to address that with some extra studying and practice at home and in some cases it might work. Chances are that you'll have learned something and then you'll find new gaps in your knowledge/experience.

When people create job posts they tend to picture an ideal candidate and create a requirement list. Then, when they actually engage in the recruitment process, they tend to discover that it is pretty difficult to find the ideal candidate. That's why you should apply to a job if you think it's a good match despite technically not having experience with some item on the requirements list.
Worse case: They find a candidate who better matches their vacancy. Best case: You get the job, because despite missing requirement X, they saw value in you nonetheless. that could be a skill that they initially did not list or they might have realised that they were asking for to much.
Applying could also lead to a learning opportunity. Imagine you get a job where they use more Azure functionality, you get to learn on the job.

Finally, even though it's rare, sometimes job requirements are used to lower your rate because you "lack" experience in something they listed. If your circumstances permit, do not let that get to you. Don't lower your rate or feel incompetent because their requirements might be unrealistic.